Amplitude MCP
OfficialAmplitude's hosted MCP server — query charts, dashboards, experiments, flags, and session replays in plain English.
Add to your client
Copy the config for your MCP client and paste it into its config file.
claude mcp add --transport http amplitude https://mcp.amplitude.com/mcpPaste into ~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"amplitude-mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.amplitude.com/mcp"
]
}
}
}Claude Desktop connects to remote servers through the `mcp-remote` proxy (installed on first run via npx). Restart Claude Desktop after saving.
Step-by-step guides: Add to Claude Desktop · Add to Cursor · Add to Windsurf
Before you start
- An Amplitude account with access to at least one project
- Appropriate project permissions in Amplitude — the server can't show anything your user can't see
- An MCP client that supports remote HTTP servers with OAuth (Claude, Cursor, ChatGPT, etc.)
About Amplitude MCP
Amplitude MCP is a hosted streamable-HTTP endpoint: the client connects to https://mcp.amplitude.com/mcp, triggers a browser OAuth 2.0 flow, and from then on every query runs as your Amplitude user. Permission mirroring is the core design — you can only reach the orgs and projects you already have access to, which makes rollout simple but also means there is no way to grant an agent narrower access than your own account.
The intended workflow is search-first: search finds dashboards, charts, notebooks, and experiments by name; get_charts / get_dashboard / get_experiments pull full definitions; then query_chart, query_metric, query_dataset, and query_experiment fetch actual numbers, including statistical significance for A/B tests. get_session_replays filters session recordings, and get_event_properties exposes your taxonomy so the agent writes correct queries.
Strengths: zero setup, a separate EU endpoint (https://mcp.eu.amplitude.com/mcp) for data residency, and coverage across analytics, Experiment, and Session Replay in one server. Trade-offs: it is beta with possible rate limits, closed source with no self-host option, and there is no API-key mode — clients must support remote HTTP servers with OAuth. The 45-star GitHub repo exists only for documentation, so judge the product by Amplitude's docs rather than repo activity.
If you need programmatic control or a local server, this isn't it; if you want product-metrics Q&A inside Claude or Cursor with your existing permission model, the one-URL setup is about as low-friction as MCP gets.
Tools & capabilities (13)
searchFind dashboards, charts, notebooks, and experiments
query_chartRetrieve data from specific charts
query_experimentAnalyze experiment results and statistical significance
query_datasetExecute custom analytics queries
query_metricGet data for specific metrics
get_chartsRetrieve full chart definitions
get_dashboardAccess dashboard content and layout
get_notebookFetch notebook content with charts and analysis
get_experimentsGet detailed experiment information
get_flagsRetrieve feature flag configurations
get_session_replaysSearch and filter session recordings
get_event_propertiesExplore event property definitions
get_contextAccess user and organization information
What this server can do
Amplitude MCP provides tools for these capabilities — tap one to see every MCP server that does the same:
When to use it
- Ask for DAU, funnel conversion, or retention numbers mid-conversation instead of building a chart by hand
- Pull A/B test results with statistical significance during a launch review
- Search session replays matching a specific behavior to debug a UX problem
- Audit which feature flags and experiments exist and how variants are performing
Quick setup
- 1Pick your endpoint: https://mcp.amplitude.com/mcp (US, default) or https://mcp.eu.amplitude.com/mcp (EU data residency)
- 2Add it as a remote MCP server in your client, e.g. claude mcp add --transport http amplitude https://mcp.amplitude.com/mcp
- 3Complete the OAuth 2.0 login when the client prompts you
- 4Test with a simple query like "What were the daily active users over the last 7 days?"
Security notes
Auth is OAuth 2.0 scoped to your existing Amplitude permissions — there is no API key to store, and organization admins can control MCP server access. Your analytics data is processed by whichever third-party AI model your client uses, so check your org's AI data-processing policy before connecting.
Amplitude MCP FAQ
Is the Amplitude MCP server free and safe to connect?
It's included with your Amplitude account — no separate charge is documented, though the beta may enforce rate limits. Access is OAuth-scoped to your existing permissions and admins can disable MCP org-wide; the main consideration is that query results flow through your AI client's model, so review your data-processing policy.
Do I need an API key?
No. Authentication is OAuth 2.0 — the client opens a browser login and tokens are managed for you. That also means agent access always follows a real Amplitude user, not a shared key you'd have to rotate.
Which endpoint should EU customers use?
https://mcp.eu.amplitude.com/mcp. The server URL must match your org's data residency region — pointing an EU org at the US endpoint results in authentication/connection errors.
Alternatives to Amplitude MCP
Compare all alternatives →
Official Elastic server: list indices, read mappings, and search with Query DSL.
Official PostHog server: product analytics, feature flags, experiments, error tracking and SQL.
Run PromQL queries and analyze Prometheus metrics from any MCP client.