You can connect Amplitude to Claude using the Model Context Protocol (MCP), and once it’s connected, Claude can pull up a chart, check a cohort, or summarize an event trend without you switching tabs to the Amplitude dashboard. Amplitude’s OAuth also just works with a new client, unlike several other tools in this series. This guide covers what Amplitude’s MCP server does, both ways to connect it — directly or through a gateway — and what’s worth checking before an AI client can read your product’s event data.

What the Amplitude MCP server actually does

Amplitude publishes a remote MCP server at mcp.amplitude.com. It exposes your project’s events, charts, and cohorts as tools Claude can call directly, so prompts like these work against your real analytics data:

  • “What happened to weekly active users after last week’s release?”
  • “Pull up the chart we built for the onboarding funnel.”
  • “How big is the cohort of users who haven’t come back in 30 days?”
  • “Did the signup event volume change this month compared to last?”

Claude reads through the same project permissions your Amplitude account already has — it’s querying live charts and cohorts, not a CSV export you’d otherwise have to pull and re-upload every time someone asks a follow-up question.

The good news: Amplitude’s OAuth just works

Several servers in gate’s directory — Figma, Vercel, Slack, HubSpot — currently only admit AI clients the vendor has allow-listed in advance, which can mean a connection attempt fails at the authorization step for no obvious reason. Amplitude isn’t one of those. Its OAuth is open to any client that asks, the same as PostHog’s, so connecting it is a standard consent-screen flow with no allow-list wall to hit. For the general pattern behind why some servers gate this and others don’t, see the unauthorized client error, explained.

Option 1: Connect Amplitude to Claude directly

Claude supports remote MCP servers natively. The short version of the setup:

  • Open Claude’s connector or MCP settings.
  • Add a remote server pointing at Amplitude’s MCP endpoint.
  • Sign in with your Amplitude account when prompted — standard OAuth, so Claude never sees your Amplitude password, and you can revoke access from Amplitude’s own account settings at any time.

That’s enough if Claude is the only AI client you use with Amplitude. The tradeoff shows up once a second client or a second teammate needs the same access: each one repeats the same OAuth grant, and each grant is its own thing to remember later.

Option 2: Connect it once, through a gateway

If you’re already juggling more than one MCP server or more than one AI client, wiring each pair directly gets old fast — the connection sprawl covered in what an MCP gateway is. The idea is to connect Amplitude (and everything else) to one gateway URL, then point every AI client at that single URL instead of repeating the OAuth step per client.

With gate specifically, connecting Amplitude looks like this: add gate’s gateway URL to Claude once, then pick Amplitude from the Amplitude server page in the directory and sign in with OAuth the same way you would directly. From then on, Amplitude’s tools are available in every client connected to your gate URL — Claude, ChatGPT, or Cursor — with the same per-tool allow, ask, or block rule applied everywhere instead of set up separately in each client. See the full list of servers set up this way on the MCP servers page.

What to check before you connect your analytics

An Amplitude project usually holds more than the one chart you had in mind when you connect it — every event, every cohort, every chart across the project. A few things worth checking:

  • Which project is actually in scope? If your Amplitude organization has more than one project — staging and production, or separate apps — know which one the connection points at before you ask Claude to summarize “our numbers.”
  • Do your events carry personal data? Event properties can include emails, names, or device identifiers depending on how your team instruments tracking. An AI client reading raw event data surfaces whatever’s actually captured, not a redacted view.
  • Read, or read and manage? Check the actual tool list rather than assuming it’s read-only — gate’s free MCP security scanner lists every tool a server exposes, so you can see whether anything on there can edit a chart or cohort definition rather than just query one.
  • Who else on the team connects it? If more than one person wires up Amplitude to their own client, a shared, revocable setup beats everyone holding their own grant to the same project — the same question covered in MCP access control for teams.

Troubleshooting the connection

  • Claude can’t find a chart you know exists. Charts and cohorts don’t carry over between separate Amplitude projects even inside the same organization — check the connection is pointed at the right one.
  • Numbers look different from the dashboard. A chart’s result can depend on the date range and filters it was built with; double-check Claude is reading the same saved chart rather than recomputing a similar-sounding one from raw events.
  • Tools disappear after an Amplitude update. Remote servers can change their tool list without warning. If you’re connected through a gateway, that’s exactly what drift detection is meant to catch — see how MCP rug pulls work for why a one-time review isn’t enough.
Where gate fits: gate’s directory lists each server’s currently verified connectivity — one-click OAuth like Amplitude, key-based, or allow-listed — so you know what kind of setup to expect before you start. Every server is scanned for prompt injection before it goes live, and every call goes into a plain-language log. See the full gateway at /mcp-gateway.

The bottom line

Connecting Amplitude to Claude with MCP is one of the easier setups in the catalog — no allow-list to wait on, just a standard OAuth consent screen. Go direct if Claude is your only client, or once through a gateway if you want the same project access shared and governed across every AI client on the team.