Connect any MCP client

Connect a client this site does not list, or call the server yourself. The address is https://agentics.you/mcp. Two sign-ins work today: OAuth, and an agent key. A console API key does not.

The address

https://agentics.you/mcp

Send POST with Content-Type: application/json and Accept: application/json, text/event-stream. The body is JSON-RPC 2.0. GET answers HTTP 405.

Sign-in

OAuth, for an app that can open a browser. A call with no token answers HTTP 401:

{"error":"invalid_token"}

The header is WWW-Authenticate: Bearer resource_metadata="https://agentics.you/.well-known/oauth-protected-resource". That document names the resource https://agentics.you/mcp and the authorization server https://agentics.you. The authorization server document lists https://agentics.you/oauth/register, https://agentics.you/oauth/authorize, and https://agentics.you/oauth/token. Grant types are authorization_code and refresh_token. The only code challenge method is S256.

Register a public client with token_endpoint_auth_method set to none. A redirect must be https, http on localhost, or a private-use app scheme. Anything else answers HTTP 400:

{"error":"invalid_redirect_uri","error_description":"redirect_uri must be https, loopback http, or a private-use app scheme"}

A good registration answers HTTP 201 with a client_id and token_endpoint_auth_method none. Then open the authorize URL with PKCE, sign in, pick the agent, choose Allow, and exchange the code at the token endpoint. Send the access token as Authorization: Bearer. It lasts one hour. The token response includes a refresh token.

An agent key, for a program that cannot open a browser. Create one under API keys, Agent keys. It starts agk_mcp_, is shown once, and is sent as Authorization: Bearer. It carries mcp:tools, receipts:read, actions:record, rules:read, and owner:ask. It does not carry hub:tasks, so whoami and send_task are not on its tool list.

A console key (ak_…) and the owner key (agk_live_…) both get the same HTTP 401 {"error":"invalid_token"}.

Copy this

A client that speaks remote MCP and OAuth needs only the URL:

{
  "mcpServers": {
    "agentics": {
      "type": "http",
      "url": "https://agentics.you/mcp"
    }
  }
}

A client that only runs a local process uses the published package @agenticstechnologies/mcp-server (npm 2.1.0). It forwards stdio to https://agentics.you/mcp and sends AGENTICS_AGENT_KEY as the bearer. It refuses a console key before it connects.

{
  "mcpServers": {
    "agentics": {
      "command": "npx",
      "args": ["-y", "@agenticstechnologies/mcp-server"],
      "env": {
        "AGENTICS_AGENT_KEY": "agk_mcp_..."
      }
    }
  }
}

Put the real key in the environment of the host, not in a file you commit. The package reads AGENTICS_AGENT_KEY. AGENTICS_API_KEY is an old name it still accepts, and it warns on stderr when that is the one set.

Python callers of the memory HTTP API, not MCP, install agentics-you from PyPI (1.2.2). The import is agentics_you. It posts to https://agentics.you/v1/memories with an ak_ key. That is the four-call quickstart, not this MCP server.

Three steps

1. Point the client at https://agentics.you/mcp over Streamable HTTP.
2. Sign in when it opens a browser, or set AGENTICS_AGENT_KEY to an agk_mcp_… key.
3. Call tools/list. The list includes remember and recall.

curl -sS https://agentics.you/mcp \
  -H "Authorization: Bearer $AGENTICS_AGENT_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Check it worked

Call remember, then recall.

curl -sS https://agentics.you/mcp \
  -H "Authorization: Bearer $AGENTICS_AGENT_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"remember","arguments":{"content":"The customer prefers email over phone."}}}'

curl -sS https://agentics.you/mcp \
  -H "Authorization: Bearer $AGENTICS_AGENT_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"recall","arguments":{"query":"how does the customer like to be contacted?"}}}'

remember returns saved true, receipt_hash, and verify_url. recall returns that memory in results, with the same hash. Open the verify link. The check does not show the memory's text.

If it does not connect

These are the bodies production returns.

Tool arguments are in the MCP tool reference. Clients with their own page: Claude, Claude Code, Codex, Gemini CLI, ChatGPT, Cursor, VS Code, Copilot CLI, Windsurf, Grok.