Amplitude MCP Server

Amplitude MCP Server is Amplitude's official Model Context Protocol integration. It makes Amplitude analytics, taxonomy, dashboards, experiments, feature flags, cohorts, and session replays accessible from MCP-capable AI clients. According to the official Amplitude documentation, users can query charts, perform ad-hoc segmentation, run funnel and retention analyses, evaluate experiment results, and manage tracking-plan definitions — all without opening the Amplitude UI or writing SQL.

The server runs as a hosted remote service. The official documentation names two regional endpoints: https://mcp.amplitude.com/mcp for the US default and https://mcp.eu.amplitude.com/mcp for EU data residency. Authentication uses OAuth 2.0. The server respects the logged-in user's existing Amplitude permissions: if a user does not have access to a project in Amplitude itself, they cannot retrieve it through an MCP client either.

Analytics and data queries

According to Amplitude's documentation, the MCP Server provides extensive analytics tools. query_chart retrieves data from existing charts, query_experiment analyzes A/B test results including statistical significance, query_dataset executes custom analytics queries, and query_metric returns data for specific metrics. The search tool finds dashboards, charts, notebooks, and experiments through free-text search.

For content access, the source documents get_charts to retrieve full chart definitions, get_dashboard for dashboard content and layout, and get_notebook for notebooks with embedded charts and analyses. get_experiments returns detailed experiment information, and get_flags provides feature-flag configurations.

Taxonomy and tracking-plan management

A key area of the server is tracking-plan management. Amplitude's documentation describes write tools for taxonomy operations: manage_amp_events creates, updates, deletes, and restores events, custom events, and labeled events, and can add newly discovered unexpected events to the plan. create_properties creates event, user, or group properties, and update_properties updates their metadata. manage_amp_data_taxonomy drives the branch workflow for tracking-plan branches: creating, updating, merging, deleting, reviewing, and refreshing branches.

According to the documentation, write operations require the RBAC action "Use MCP (write)". This permission level is controlled by organization administrators, enabling granular access control within MCP access.

Session replay and user insights

get_session_replays enables searching and filtering session recordings based on criteria. This allows finding user sessions that match specific events, errors, or behavioral patterns without opening the Amplitude interface. get_event_properties explores event-property definitions, and get_context returns user and organization information.

The official documentation also describes Progressive Tool Discovery: by appending ?discovery=progressive to the server URL, the client starts with a minimal tool set and discovers tools on demand. This reduces token usage in long-running agent sessions.

Security, data access, and boundaries

All requests through the Amplitude MCP Server leave the local machine and are processed via Amplitude's cloud. The documentation states: "Third-party AI models process your data during analysis." This means the prompt, tool call, result, and database queries can be passed to the selected AI model provider (such as Anthropic, OpenAI, or Google) and to the Amplitude API. Review the privacy and retention policies of both providers before sensitive customer data enters queries.

According to the documentation, the Amplitude MCP Server is exclusively a read and write tool for analytics content — not an event ingestion endpoint. Production events must still be sent through an Amplitude SDK or the HTTP V2 API. The manage_amp_events tool registers event definitions in the tracking plan but does not send event data.

Organization administrators can restrict MCP access through RBAC roles. The documentation describes two separate roles: one for read access and one for write operations. This allows granting specific user groups read-only or full MCP access. The documentation recommends assigning roles deliberately rather than enabling organization-wide access.

The server is in beta according to the README and documentation. Amplitude notes that not all features may be available and that rate limits apply. Plan for appropriate error handling in production-critical analytics workflows.

AI Context and reference files

Amplitude's documentation describes the get_amplitude_context tool: when called with a project ID, it returns the organization-specific AI Context configuration — metric definitions, terminology, and business rules that the user has configured in Amplitude AI Controls. The documentation recommends calling this tool at the start of a session so the AI client works with the correct metrics and terminology.

For repo-side instrumentation conventions, Amplitude documents an optional .amplitude/instrumentation-agent-context.md file at the repository root. Marketplace skills such as instrument-events read this file automatically.

The public GitHub repository amplitude/mcp-server-guide contains only a guide and README; there is no public open-source repository of the actual MCP server. On 2026-09-08, the GitHub API reported exactly 45 stars. This number is a popularity signal for the guide repository, not a quality indicator for the hosted service.

FAQ

Can the Amplitude MCP Server ingest events? No. According to the official documentation, the MCP Server is not an ingestion endpoint. Use an Amplitude SDK or the HTTP V2 API for event tracking.

Is a new Amplitude license required? According to the documentation, any existing Amplitude customer can use the MCP Server from a compatible client. Review current account terms directly with Amplitude.

Can other users access my data? No. The server respects existing Amplitude permissions. Organization administrators additionally control MCP access through RBAC.

Which endpoint is correct for EU data residency? The documentation names https://mcp.eu.amplitude.com/mcp for EU residency.

An existing Amplitude account, an MCP-capable AI client with OAuth support, and appropriate project permissions in Amplitude.

US: add https://mcp.amplitude.com/mcp in the AI client as a Remote MCP server and complete OAuth 2.0. EU: use https://mcp.eu.amplitude.com/mcp. Token-efficient mode: append ?discovery=progressive to the URL.

OAuth 2.0. The server inherits the authenticated user's existing Amplitude permissions. Organization administrators control MCP access through RBAC roles.

Access is limited to the Amplitude projects and data the authenticated user is permitted to see in Amplitude itself. Write access requires the RBAC action "Use MCP (write)".

Requests and responses are processed through Amplitude's cloud. According to the provider, third-party AI models process data during analysis. Review the privacy and retention policies of both Amplitude and the selected model provider.

Amplitude analytics data and user data enter the context of the connected AI client and model. MCP access is controllable through RBAC. Beta status: rate limits and missing features are possible.