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.

If you need your project's analytics data, such as charts, cohorts, events, or guide and survey drafts, use the authenticated Amplitude MCP Server instead. It also covers your taxonomy and tracking plan. To compare the two servers, refer to Amplitude MCP and Docs MCP compared.

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.

Docs MCP and Amplitude MCP compared

The Docs MCP server reads public documentation without sign-in. The Amplitude MCP Server reads and writes your organization's Amplitude data through OAuth.

Docs MCP serverAmplitude MCP Server
Primary purposeSearch and retrieve public Amplitude documentation from an AI client.Query, create, and edit Amplitude analytics, taxonomy, and content from an AI client.
AuthenticationNone. The server is public.OAuth sign-in with your Amplitude account, or service accounts for non-interactive agents.
Data accessPublic English Amplitude documentation only.Your organization's analytics, taxonomy, charts, dashboards, notebooks, cohorts, experiments, and other content, limited to what your account can access.
Read and writeRead-only.Read and write.
Toolsget_page, list_pages, and search_docs.Refer to Available tools and capabilities.
Supported clientsClients that support Streamable HTTP and accept a direct URL, such as Claude Code, Cursor, and Codex CLI.MCP-capable clients such as Cursor, Claude, ChatGPT, Codex, and Gemini.

For endpoints and the workflows each server supports, refer to Amplitude MCP and Docs MCP compared and Workflow boundaries.

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.

WebMCP (experimental)

When you visit Amplitude docs in a WebMCP-capable browser, the page registers browser-native tools that in-tab AI agents can call directly. This complements the remote Docs MCP server. IDE agents should still use https://amplitude.com/docs/api/mcp.

WebMCP tools available on the docs site:

  • search_docs
  • get_page
  • navigate_to_page
  • get_current_page

WebMCP requires Chrome 149+ (origin trial) or the chrome://flags/#enable-webmcp-testing flag. Tools aren't available in headless browsers.

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?

For AI agents: a documentation index is available at /docs/llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.

On this page