Set up Amplitude MCP Server
Connect the official Amplitude Remote MCP via OAuth and safely query analytics data from AI clients.
- Skill Road
- Set up Amplitude MCP Server
Published on 18.09.2026
Amplitude MCP Server brings Amplitude analytics, dashboards, experiments, feature flags, and tracking-plan tools into an MCP-capable AI client. The official documentation names two regional remote endpoints: https://mcp.amplitude.com/mcp for the US default and https://mcp.eu.amplitude.com/mcp for EU data residency. No local installation is required — the connection is made through OAuth 2.0 from within the client.
Before connecting: clarify the task and permissions
Before setup, make sure you have access to the relevant projects in Amplitude. The MCP Server inherits exclusively the permissions of the authenticated Amplitude user; there is no separate service account. If you want to use write operations — creating or modifying events, properties, branches, or dashboards — an organization administrator must assign you the RBAC action "Use MCP (write)". Read-only access is sufficient for purely analytical tasks.
Think ahead about which data should enter the AI client. According to Amplitude's documentation, third-party AI models process data during analysis. Queries, results, and chart data can therefore be passed to the model provider used by the connected client. For sensitive customer data or regulated information, review the privacy policies of both Amplitude and the selected model provider before including them in queries.
Connect the Remote MCP via OAuth
Open the MCP configuration of the chosen client and add the regional server URL. For the US default: https://mcp.amplitude.com/mcp. For EU data residency: https://mcp.eu.amplitude.com/mcp. The client then opens an OAuth 2.0 authorization dialog. Sign in with the Amplitude account that has access to the relevant projects and grant the requested permissions. After successful completion, the MCP Server is active.
For Claude Code, the official documentation describes HTTP transport and a browser-based OAuth flow as an example. Cursor, ChatGPT, and other compatible clients follow their respective MCP configuration steps. Consult the documentation of your specific client for the exact configuration steps.
To reduce token costs, Amplitude documents a Progressive Discovery mode: append ?discovery=progressive to the URL — for example https://mcp.amplitude.com/mcp?discovery=progressive. In this mode, the client starts with a minimal tool set and discovers additional tools on demand via list_tool_categories and get_category_tools.
Use AI Context for better results
The official documentation recommends calling get_amplitude_context with a project ID at the start of each session. This tool returns the configurations stored in Amplitude AI Controls: metric definitions, terminology, and business rules for your organization. When the AI client has this information, it works with the correct terms and metrics in follow-up queries, which reduces misunderstandings about definitions.
Organization administrators can configure AI Context in the Amplitude dashboard under AI Controls: Markdown text instructions and uploaded reference documents. The text instructions are returned by get_amplitude_context; uploaded files are available to in-product Agents but not directly retrievable through MCP tools. Therefore, put rules and definitions that the MCP client should know in text instructions.
First queries and typical workflows
Start with a simple search query: "Find all dashboards about onboarding." This tests the connection and shows which projects the client can access. Then try query_chart for a known chart or get_dashboard for an existing dashboard.
A typical analysis workflow according to Amplitude's documentation: search for relevant content with search, retrieve chart definitions with get_charts, run custom queries with query_dataset, and ask follow-up questions based on results. For experiments: get_experiments returns metadata, query_experiment the statistical results.
For Session Replay: get_session_replays with filter criteria such as event name, user attribute, or time range. The result contains matching session IDs and metadata that you can open directly in the Amplitude interface.
Write operations: managing the tracking plan
If you have the RBAC action "Use MCP (write)", you can make tracking-plan changes. Use manage_amp_data_taxonomy to create a branch before changing event definitions — this keeps changes separable and reviewable. manage_amp_events creates new events or updates existing ones. create_properties and update_properties manage properties.
Important: these tools modify tracking-plan definitions in Amplitude Data. They do not send production events. For sending events, use an Amplitude SDK or the HTTP V2 API.
Security, rate limits, and beta status
The Amplitude MCP Server is in beta according to the README and documentation. Rate limits are documented and may change. Plan for appropriate error handling in production workflows and test new features in a test environment first.
Organization administrators can restrict MCP access through AI Controls in the Amplitude dashboard. The documentation describes a separate RBAC role for write operations. Enable write access only for users who genuinely need it. For teams, it is advisable to initially enable only read access and to release write operations deliberately.
Amplitude analytics data — including user segments, event volumes, and experiment results — is sensitive product data. It should not end up in public chats, screenshots, or unauthorized systems. After each setup, check which data the client can actually retrieve and limit queries to what is necessary.
FAQ
Which endpoint is correct for EU data residency? The documentation names https://mcp.eu.amplitude.com/mcp.
Can I use the MCP Server for event tracking? No. According to the official documentation, the MCP Server is not an ingestion endpoint. Use an Amplitude SDK or the HTTP V2 API for production events.
What is Progressive Discovery mode? Appending ?discovery=progressive to the server URL reduces the initially transmitted tool set. The client discovers tools on demand, which reduces token costs.
Do I need a special Amplitude license? According to the documentation, all existing Amplitude customers can use the MCP Server. Review account limits and terms directly with Amplitude.
Frequently asked questions
Which endpoint is correct for EU data residency?
The official documentation names https://mcp.eu.amplitude.com/mcp for EU residency.
Can I send events through the MCP Server?
No. The MCP Server is not an ingestion endpoint. Use an Amplitude SDK or the HTTP V2 API for production events.
What does Progressive Discovery mode do?
Appending ?discovery=progressive to the URL reduces initial token usage because the client discovers tools on demand instead of loading all at once.