DE

Kepos · MCP

Connect Cursor to Kepos via MCP — Kepos

Connect Cursor to Kepos from mcp.json with a scoped bearer token, or use OAuth discovery for an OAuth-capable MCP setup in your selected workspace.

What you need

  • A Kepos account and either a token from /me/mcp-tokens or an OAuth-capable Cursor setup.
  • A Cursor project or user MCP settings file.
  • The remote server URL https://kepos.app/mcp.

Set up Cursor

  1. 1

    Create access

    Sign in to Kepos, open /me/mcp-tokens, create a token for Cursor, and copy its secret immediately. The token UI lets you choose the scopes and spaces the client may reach. OAuth-capable clients may use Kepos's OAuth discovery instead; the discovery document advertises authorization, token, and registration endpoints.

  2. 2

    Add Kepos to the client

    Use this client configuration and replace the example token with the secret you copied.

    {
      "mcpServers": {
        "kepos": {
          "url": "https://kepos.app/mcp",
          "headers": { "Authorization": "Bearer mn_YOUR_TOKEN" }
        }
      }
    }
  3. 3

    Save and connect

    Save the configuration, restart or reconnect Cursor, and use https://kepos.app/mcp as the remote MCP server. The endpoint accepts Streamable HTTP requests and returns the MCP session id for subsequent calls.

Run the first function test

After Cursor reports the server as connected, have the agent read agent-onboarding and call chat_register. Do not start by creating a note: search_notes must come first in the same session.

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

401 Unauthorized or an authentication error

Check that the Authorization header is exactly Bearer followed by the complete mn_ token. Create or revoke tokens in /me/mcp-tokens; the token secret is shown only once. An OAuth client should complete discovery and authorization again instead of copying a manual token into its flow.

428 ONBOARDING_REQUIRED

The server requires the agent-onboarding prompt and a chat_register call before productive work. Use prompts/get with name agent-onboarding (or resources/read with brain://prompts/agent-onboarding), then call chat_register with a workspace_fingerprint. Tool-only clients can call read_onboarding.

412 SEARCH_FIRST_REQUIRED when creating a note

Call search_notes before create_note in the same session. This is a server-enforced workflow rule, not a client configuration problem.

The mcp.json shape is a Cursor client convention. Endpoint and workflow facts come from this repository’s Streamable HTTP route and MCP tool implementations.