Amplitude MCP Server – Product Analytics Context
Amplitude's official MCP servers connect AI assistants to Amplitude analytics and documentation. Use the authenticated Amplitude MCP server to query and create analytics content with OAuth-secured account permissions, or use the public Docs MCP server for read-only Amplitude documentation search.
Overview
Amplitude provides official MCP servers that let AI assistants work with Amplitude product analytics and documentation. The authenticated Amplitude MCP server connects AI clients to product data, experiments, cohorts, charts, dashboards, taxonomies, and related Amplitude content. The separate Docs MCP server gives unauthenticated, read-only access to public Amplitude documentation.
What the MCP server enables
The authenticated Amplitude MCP server lets teams analyze product data, experiments, and user behavior from MCP-compatible tools such as Claude, Cursor, ChatGPT, Lovable, Kiro, Gemini CLI, Codex CLI, and other clients that support remote MCP over Streamable HTTP.
Documented capabilities include:
- Querying analytics, metrics, charts, dashboards, notebooks, and dashboard content.
- Creating and editing Amplitude content such as charts, dashboards, notebooks, cohorts, and experiment-related assets where permissions allow.
- Working with taxonomy and tracking plans, including events, properties, branches, and tracking-plan cleanup workflows.
- Asking natural-language questions about user behavior, conversion, retention, experiment results, feature flags, and product metrics.
- Using progressive tool discovery to reduce token spend and discover tool schemas on demand.
The public Docs MCP server supports get_page, list_pages, and search_docs for English Amplitude documentation.
When to use it
Use Amplitude MCP when an AI workflow needs trusted behavioral analytics context from an Amplitude organization. Practical examples include asking for daily active users, analyzing signup conversion by traffic source, summarizing an executive dashboard, investigating a metric spike, reviewing experiment performance, creating a launch dashboard, auditing tracking plans, or finding stale feature flags.
Use Docs MCP when an agent only needs public Amplitude documentation and should not access private product data.
Connection and authentication
The authenticated Amplitude MCP server uses Streamable HTTP and OAuth 2.0. Use the server that matches the organization's data residency:
- US:
https://mcp.amplitude.com/mcp - EU:
https://mcp.eu.amplitude.com/mcp
Progressive discovery is available by adding ?discovery=progressive to either URL.
The Docs MCP server is:
https://amplitude.com/docs/api/mcp
Docs MCP is public, read-only, unauthenticated, English-only, and supports Streamable HTTP only. Older clients that only support deprecated HTTP+SSE do not work with that endpoint.
Key considerations
Amplitude MCP respects the authenticated user's existing Amplitude permissions and provides no additional access beyond the user's normal Amplitude account privileges. Organization administrators can allow, block, or scope MCP use through content access and role-based controls such as Use MCP read and write actions. The AI client processes the Amplitude data returned through MCP, so organizations should review privacy, compliance, and data-governance policies before connecting. Amplitude notes that tool availability may evolve and that large or complex queries can hit client token or timeout limits.
Supported Transports
streamable_http
URL: https://mcp.amplitude.com/mcp
streamable_http
URL: https://mcp.eu.amplitude.com/mcp
streamable_http
URL: https://mcp.amplitude.com/mcp?discovery=progressive
streamable_http
URL: https://mcp.eu.amplitude.com/mcp?discovery=progressive
streamable_http
URL: https://amplitude.com/docs/api/mcp
Frequently Asked Questions
- When should an AI agent use the Amplitude MCP server?
- Use it when an AI workflow needs Amplitude product analytics context, such as querying active users, analyzing conversion funnels, summarizing dashboards, investigating metric spikes, reviewing experiment results, creating charts or dashboards, managing cohorts, or auditing tracking plans.
- What does the Amplitude MCP server add to an AI agent's capabilities?
- It gives the agent OAuth-secured access to Amplitude product data and content, including analytics, charts, dashboards, experiments, cohorts, feature flags, session and user-behavior context, taxonomies, and tracking plans. The separate Docs MCP server gives public read-only access to Amplitude documentation.
- What can an AI agent access or manage through Amplitude MCP?
- Depending on the user's permissions, the agent can query and create Amplitude content such as charts, dashboards, notebooks, cohorts, experiment assets, and tracking-plan resources. The public Docs MCP endpoint only supports documentation tools such as get_page, list_pages, and search_docs.
- How is authentication configured for the Amplitude MCP server?
- The authenticated Amplitude MCP server uses OAuth 2.0 and respects the user's existing Amplitude permissions. The public Docs MCP server at https://amplitude.com/docs/api/mcp requires no authentication and is read-only.
- Which transport should be used for the Amplitude MCP server?
- Use Streamable HTTP with https://mcp.amplitude.com/mcp for US data residency or https://mcp.eu.amplitude.com/mcp for EU residency. Add ?discovery=progressive to reduce the initial tool list. Use https://amplitude.com/docs/api/mcp only for public documentation search.