Connect an MCP client via HTTP — Kepos

What you need

• A Kepos account with a token from /me/mcp-tokens, or an OAuth-capable client.
• A client that supports the MCP Streamable HTTP transport.
• The endpoint https://kepos.app/mcp and, for manual auth, an Authorization: Bearer header.

Connect the protocol

1. 1

   Choose authentication

   For a manual connection, create a token in /me/mcp-tokens and send it as a bearer token. For OAuth, use the authorization-server discovery document at /.well-known/oauth-authorization-server; it advertises /api/oauth/authorize, /api/oauth/token, and /api/oauth/register.

2. 2

   Initialize the MCP session

   POST an MCP initialize request to the endpoint. Kepos negotiates supported protocol versions and returns capabilities for tools, resources, and prompts.

   POST https://kepos.app/mcp
   Authorization: Bearer mn_YOUR_TOKEN
   Content-Type: application/json
   
   {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-11-25","capabilities":{},"clientInfo":{"name":"your-client","version":"1.0"}}}

3. 3

   Keep the session identity

   Echo the Mcp-Session-Id response header on subsequent requests. Then use prompts/get or resources/read for agent-onboarding and call chat_register before productive tools.

Run the first function test

Verify the complete onboarding path with the prompt and registration calls below. A successful chat_register response establishes an agent session; after that, tools/list and search_notes are useful read-only checks.

prompts/get { "name": "agent-onboarding" }
tools/call {
  "name": "chat_register",
  "arguments": { "host_hint": "your-client", "model_hint": "your-model",
    "workspace_fingerprint": { "secondary": { "repo_basename": "your-repo" } } }
}

Troubleshooting