Official remote MCP server for querying and creating Amplitude analytics, dashboards, experiments, cohorts, session replay insights, and product data from Claude and other MCP clients.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
6 safety and 4 privacy notes across 7 risk areas. Review closely: credentials & tokens, permissions & scopes, network access, third-party handling.
{
"mcpServers": {
"amplitude": {
"url": "https://mcp.amplitude.com/mcp"
}
}
}Amplitude MCP Server is Amplitude's official remote Model Context Protocol server for bringing product analytics into AI clients. It lets Claude Code and other MCP-capable tools query Amplitude content, inspect product behavior, work with experiments, and create or edit Amplitude resources through natural language.
The server is useful for teams that already rely on Amplitude dashboards, experiments, cohorts, session replay, and feedback workflows. Instead of asking Claude to reason from pasted screenshots or stale exports, users can connect the assistant to live Amplitude context through OAuth and the existing Amplitude permission model.
Amplitude documents two product-data endpoints:
https://mcp.amplitude.com/mcphttps://mcp.eu.amplitude.com/mcpUse the EU endpoint only when the relevant Amplitude data is in the EU region.
?discovery=progressive to keep the initial
tool list small and discover schemas on demand.Add the standard Amplitude MCP endpoint as a remote HTTP server:
claude mcp add -t http -s user amplitude https://mcp.amplitude.com/mcp
Open the MCP connection in Claude Code and complete the Amplitude OAuth flow. Make sure you authenticate with the right Amplitude organization and project.
For EU-resident Amplitude data, use the EU endpoint instead:
claude mcp add -t http -s user amplitude-eu https://mcp.eu.amplitude.com/mcp
For large organizations or token-sensitive workflows, use progressive discovery:
claude mcp add -t http -s user amplitude https://mcp.amplitude.com/mcp?discovery=progressive
Then ask Claude to call get_context, list_tool_categories,
get_category_tools, and describe_tool before using a specific analytics,
dashboard, experiment, cohort, or replay tool.
Amplitude MCP uses the current user's Amplitude permissions, but the data it returns still enters the connected AI client and model session. Treat it as a production data integration. Keep access limited to approved users, use admin controls when AI access is not allowed, and require confirmation before any write-capable tool creates or changes Amplitude content.
Show that Amplitude MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/amplitude-mcp-server)Amplitude MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
| Field | Official remote MCP server for querying and creating Amplitude analytics, dashboards, experiments, cohorts, session replay insights, and product data from Claude and other MCP clients. Open dossier | Query Mixpanel analytics data from Claude — run insights, funnels, flows, retention analysis, manage dashboards, explore events and properties, run experiments, and analyze session replays — with the official Mixpanel remote MCP server. Open dossier | Query observability data, manage dashboards, and monitor your systems from Claude — run APL queries against datasets, list metrics, inspect monitors, and retrieve saved queries — with the official Axiom remote MCP server. Open dossier | Manage A/B tests and feature flags in GrowthBook from Claude — list and create experiments, toggle rollouts, review test results, and interact with your GrowthBook workspace — with the official GrowthBook MCP server. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | JSONbored | — | — | — |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | — |
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | Amplitude | Mixpanel | Axiom, Inc. | GrowthBook |
| Added | 2026-06-05 | 2026-06-18 | 2026-06-18 | 2026-06-18 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓The authenticated Amplitude MCP server can expose tools that create and edit analytics content, not just read existing dashboards. Use the existing Amplitude permission model and keep users scoped to the projects and organizations they are allowed to inspect. Require human confirmation before Claude creates dashboards, edits notebooks, changes experiments, creates cohorts, updates metrics, or touches feature-flag workflows. Use the EU MCP endpoint only when the Amplitude data resides in the EU region; otherwise use the standard US endpoint. Consider progressive discovery to reduce tool-list size and force the assistant to describe a tool schema before calling higher-impact tools. Organization administrators can restrict or disable MCP access in Amplitude content access settings; use that control if AI access is not approved. | ✓The server is hosted by Mixpanel and authenticated via OAuth — your existing Mixpanel project permissions are automatically applied. The MCP server grants read and write access to your Mixpanel project; it can create and modify dashboards, reports, and feature flags. Treat Service Account credentials as secrets; do not commit them to repositories. | ✓The MCP server includes dashboard management tools (create, update, delete) — review any write operations before confirming. APL queries run against live datasets; complex queries over large time windows may be slow or consume significant dataset quota. | ✓`create_experiment` and `create_feature` write to your GrowthBook workspace — capabilities are scoped by your API key/PAT permissions. Creating experiments or feature flags may immediately affect production if they are in a live environment — review before confirming. |
| Privacy notes | ✓Amplitude MCP can expose product analytics, event data, user cohorts, experiment results, dashboard definitions, session replay context, feedback summaries, AI agent analytics, and account health signals to the connected AI client. AI providers may process the Amplitude data returned through MCP; review internal AI, privacy, GDPR, CCPA, and customer-data policies before connecting production projects. Assistant transcripts, MCP client logs, screenshots, support tickets, and exported chats can retain user identifiers, cohort definitions, behavioral data, experiment details, and roadmap-sensitive product insights. OAuth ties access to the current Amplitude user, but it does not make downstream model transcripts private by itself. | ✓Queries and analytics results (event data, user properties, funnel metrics) are sent through Mixpanel's hosted MCP infrastructure. Session replay summaries and user segment data may surface in Claude's context — treat these as sensitive product analytics. | ✓Log data, traces, metrics, and monitor configurations from your Axiom datasets and organization are surfaced in Claude's context. OAuth is the recommended authentication method — no API token is stored in your MCP configuration. | ✓Experiment configurations, feature flag definitions, targeting rules, and experiment results from your GrowthBook workspace are surfaced in Claude's context. Your `GB_API_KEY` is a secret — store it as an environment variable, not in version-controlled config files. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Source-backed guides for putting this to work.
Review remote MCP OAuth and token-audience handling before connecting clients.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.