Setup Guide

Connect an MCP-compatible client to your Kept projects.

Before you start#

Create a personal token in Settings → API keys. Use the complete geo_ token. You need access to at least one project to read project analytics; an account with no visible projects returns an empty project list.

Configure your client#

{
  "mcpServers": {
    "kept": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://app.keptai.com/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:${KEPT_AUTH_HEADER}"
      ],
      "env": {
        "KEPT_AUTH_HEADER": "Bearer <geo_token>"
      }
    }
  }
}

{
  "mcpServers": {
    "kept": {
      "url": "https://app.keptai.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:KEPT_API_TOKEN}"
      }
    }
  }
}

claude mcp add --transport http kept https://app.keptai.com/mcp \
  --header "Authorization: Bearer $KEPT_API_TOKEN"

For Claude Desktop, install Node.js and use the mcp-remote bridge in your local configuration file. Replace the placeholder token and restart the client after saving. For Cursor, make KEPT_API_TOKEN available to the client process; the variable must contain the token, without the Bearer prefix. For Claude Code, set KEPT_API_TOKEN in your shell before running the command.

Verify the connection#

Reconnect the client and ask it to list the available Kept tools. There are ten read-only tools. Call list_projects first, then use a returned host with get_overview or another project tool.

Troubleshooting#

• 401: check the token value, header, and revocation status.
• No projects: confirm which projects the token’s account can access.
• 429: respect Retry-After; the service allows 600 authenticated POST messages per token per UTC hour, including initialization and notifications.
• Tool error: inspect isError and the message before retrying. Check the host and tool arguments.

See Available tools for the exact arguments.