On this page

Docs MCP server

Docs content only

This article covers the Docs MCP server, which serves public Amplitude documentation only. It doesn't connect to your Amplitude organization and can't access analytics data, AI Context, tracking plans, charts, or any other product content.

For authenticated MCP access to your Amplitude Analytics data, taxonomy, and tracking plan, use the Amplitude MCP Server instead.

The Amplitude Docs MCP server is a public, read-only MCP endpoint at https://amplitude.com/docs/api/mcp that serves English Amplitude documentation to supported AI clients over Streamable HTTP. Connect a client such as Claude Code, Cursor, or Codex CLI to fetch a page, list pages, or search docs from inside the client.

Use the Docs MCP server only for read-only access to public documentation. Don't use it for analytics queries, tracking plan changes, or any task that requires your Amplitude account.

Supported clients

Use a client that supports remote MCP servers over Streamable HTTP and accepts a direct URL. Examples include Claude Code, Cursor, and Codex CLI.

Older MCP clients that only support the deprecated HTTP+SSE transport don't work with this endpoint.

Add the server

Many MCP clients support a simple JSON config:

json
{
  "mcpServers": {
    "amplitude-docs": {
      "url": "https://amplitude.com/docs/api/mcp"
    }
  }
}

If your client supports command-line setup, add the same URL as a remote HTTP MCP server:

shell
claude mcp add -t http -s user amplitude-docs https://amplitude.com/docs/api/mcp

Available tools

  • get_page: Returns the full markdown content for one docs page.
  • list_pages: Lists available page titles and slugs.
  • search_docs: Searches English docs content by keyword.

Each tool accepts an optional rationale string (max 500 characters) so the model can explain why it called the tool. That value may appear in server usage telemetry when enabled.

Optional correlation headers

MCP clients may send these HTTP headers on each request. The server copies them into usage telemetry when present:

  • x-agent-trace-id
  • x-agent-session-id
  • x-mcp-client (for example, cursor or claude-code)

Limitations

  • The server is public and doesn't require authentication.
  • The server is read-only.
  • The server serves English docs content only.
  • The server doesn't expose MCP prompts or resources in v1.
  • The endpoint supports Streamable HTTP only.
If you need authenticated access to Amplitude product data, use the Amplitude MCP Server instead. To decide which interface fits each job when you build an AI agent, refer to Choose an interface for AI agents.

Troubleshooting

  • If your client reports an unsupported transport, update the client to a version that supports remote MCP servers over Streamable HTTP.
  • If install fails, confirm that you used the exact endpoint URL: https://amplitude.com/docs/api/mcp.
  • If you need private analytics data or write access, this server isn't the right endpoint. Use the authenticated Amplitude MCP Server.

Was this helpful?