MCP

Autographical exposes an MCP server that any compatible client can connect to.

Server URL


https://api.autographical.ai/mcp

Authentication

The MCP server accepts both OAuth tokens and API keys.

OAuth

The server supports OAuth 2.1 with Dynamic Client Registration. MCP clients that support OAuth (such as Claude Code) will discover the auth flow automatically via the server’s .well-known endpoints.

API key

Create an API key in your Autographical user settings and pass it as a Bearer token via the Authorization header:


Authorization: Bearer <token>

Tools

`recent_activity`

Returns sessions and top resources from the last 48 hours and 7 days respectively.

`search`

Hybrid search across resources, sessions, and activity interactions. Supports natural language queries, quoted phrases, and exclusions.

Parameter	Type	Required
`query`	string	yes

`get_resource`

Returns detailed information about a specific resource, including attention metrics, recent sessions, and a content preview.

Parameter	Type	Required
`url_or_id`	string	yes

`get_resource_content`

Returns the full extracted text content of a resource (up to ~10,000 characters).

Parameter	Type	Required
`url_or_id`	string	yes

`get_session`

Returns full session details including all resources and their interactions.

Parameter	Type	Required
`session_id`	string	yes

Clients

Generic MCP client


{
  "mcpServers": {
    "autographical": {
      "type": "http",
      "url": "https://api.autographical.ai/mcp",
    }
  }
}

To use API key authentication instead of OAuth, include the Authorization header:


{
  "mcpServers": {
    "autographical": {
      "type": "http",
      "url": "https://api.autographical.ai/mcp",
      "headers": {
        "Authorization": "Bearer <your-api-key>"
      }
    }
  }
}

Claude Code

See Claude Code — MCP for setup instructions, using either the plugin or manual configuration.