Our grade: 4 checks
Based on public data, not a full audit. See how we grade. Something changed? Request a re-grade.
Community rating
- 5 1
- 4 1
- 3 3
- 2 0
- 1 0
Trust in production
- Trust it - 20%
- With caveats - 60%
- Wouldn't - 20%
80% would recommend this server
How reviewers scored it
- Setup & docs 4.0
- Auth experience 4.4
- Reliability 3.8
- Maintainer responsiveness 4.8
Why it got an A
Amplitude's hosted MCP server at mcp.amplitude.com/mcp (EU projects use mcp.eu.amplitude.com/mcp), closed source, over streamable HTTP. You sign in with Amplitude through OAuth, so there are no API keys, and calls act as you: only projects your account can reach, with your role in each. The linked repo is Amplitude's own plugin marketplace, a wrapper that points clients at the hosted URL, not the server code, so this grade rests on Amplitude's docs. Per the docs, reading covers search, context and query tools plus user, taxonomy, session replay and data warehouse lookups. It also writes: charts and chart monitors, dashboards, notebooks, experiments, feature flags, cohorts (create and sync), metrics, sharing and comments, and manage_amp_events, manage_amp_properties and manage_amp_branches, which include delete and restore, plus a run_amp passthrough. Writes need the "Use MCP (write)" role action on the project. Service-account auth for unattended agents is an Enterprise feature and a Plus add-on, not on Free or Growth. No advisories on record. Biggest deduction: nothing here can be inspected, so server upkeep, shell-out behaviour and the passthrough tool rest on Amplitude's word, and the write set reaches feature flags and experiments. Withhold the write role action from your AI sign-in unless you need it, and keep tool approval on for flag, experiment and delete calls.
How to connect
claude mcp add --transport http amplitude https://mcp.amplitude.com/mcp
Is Amplitude MCP Server safe?
Is Amplitude MCP Server safe to use?
Amplitude MCP Server grades A (strong public trust signals). Upkeep is hard to verify (closed source or a single maintainer), so pin the version you tested. It runs locally over stdio, so it acts with your machine's access.
Does Amplitude MCP Server have known vulnerabilities?
Not in our current data: it has no open CVEs or advisories. We re-check as new ones are published.
Does Amplitude MCP Server support authentication?
Yes. It requires a login, so access can be tied to a person or a scoped key.
Alternatives in Developer Tools
- A Appwrite MCP ServerOfficial Appwrite server that exposes databases, users, functions, teams and storage as tools, hosted with OAuth or run locally with a project API key.
- A Atlassian Rovo MCP ServerOfficial hosted Atlassian server for Jira, Confluence, Jira Service Management, Compass, Bitbucket, Loom, Goals, Projects, and Teams, with OAuth 2.1 sign-in.
- A Better Stack MCP ServerOfficial hosted Better Stack server to read and manage incidents, monitors, status pages and on-call, and run SQL over your logs, spans and metrics, with OAuth or an API token.
- A Buildkite MCP ServerOfficial Buildkite server for pipelines, builds, jobs, logs, annotations, and Test Engine data, hosted or local.
- A Checkly MCP ServerOfficial hosted Checkly server to read check results, root-cause analyses and status pages, and to create, change, delete and run checks and post incidents, with OAuth or an API key.
Community reviews
The Amplitude integration I wanted
Hooked Amplitude MCP Server into Claude Code and it worked on the first try. Hosted endpoint means no local process to babysit. Sign-in flow was painless and I never had to paste a key into a config file. Filed an issue and got a reply within two days. It is in our production agent and I sleep fine.
Used for Pairing with Claude Code on a monorepo
- Setup & docs 5/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Does the job, docs could be better
Took longer to configure than I expected. Auth is handled properly, and revoking access later was one click. The OAuth flow worked first time in Claude Code.
Used for Scripting routine maintenance tasks
- Setup & docs 4/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Mixed feelings after two weeks
Works well enough for what I need. I like that access goes through a proper sign-in instead of a long-lived secret on disk.
Used for Internal developer assistant
- Setup & docs 3/5
- Auth experience 3/5
- Reliability 3/5
- Maintainer responsiveness 5/5
Clean integration, sensible permissions
Installed it on a Friday, it was part of my workflow by Monday. The OAuth flow worked first time in Claude Code. I like that access goes through a proper sign-in instead of a long-lived secret on disk.
Used for Onboarding new devs with an agent that answers repo questions
- Setup & docs 5/5
- Auth experience 4/5
- Reliability 4/5
- Maintainer responsiveness 4/5
Decent, not set-and-forget
Mostly reliable, with the odd timeout. Nothing to install, I just point the client at the URL. Gave it its own API key so I can revoke it without breaking anything else. Keeping it to local experiments for now.
Used for Generating boilerplate from existing patterns
- Setup & docs 3/5
- Auth experience 5/5
- Reliability 4/5
- Maintainer responsiveness 5/5
Write a review
Ran this server? Tell other teams how it went. You get one review per server. We email you a link to confirm it, then an editor checks it before it goes up. We never show your email.