Skip to main content
Back to the Amplitude MCP server

MCP Gateway · Claude

Amplitude icon

Connect Amplitude to Claude

Most product questions end in Amplitude, but not everyone knows how to build the chart. With Amplitude behind the Speakeasy MCP Gateway, anyone in Claude can ask about active users, funnels or retention in plain language, check what customers say in feedback, and find the dashboards a team already maintains. Each person only sees the servers their role can reach.

Category
Data & analytics
Tools
44
Authentication
OAuth
Claude
Web, desktop and mobile

Behind the MCP Gateway

Run Amplitude MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Amplitude call inspected and logged.

Deploy on MCP Gateway

Before you start

What Amplitude needs first

An Amplitude organization admin does the Amplitude side of the setup.

  • There is nothing to create in Amplitude. Users sign in with their own accounts and keep their existing permissions.
  • US and EU organizations use different server URLs, and the two are not interchangeable.
  • Custom roles need Use MCP (read) enabled, or MCP calls fail for that role.

In Amplitude

  1. Find your data region from the Amplitude hostname and record the matching server URL.
  2. In Settings, Content Access > MCP, confirm the MCP server is allowed.
  3. For custom roles, enable Use MCP (read), and Use MCP (write) only if needed.
Full Amplitude setup guide in the docs

Set up

Add Amplitude to Claude in 4 steps

  1. 01

    Add Amplitude from the catalog

    An admin finds Amplitude in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Amplitude uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Amplitude

    Give teams the mcp:connect scope on the Amplitude server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Amplitude to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Claude

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use Amplitude from Claude

    The first time Claude connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Amplitude needs its own OAuth grant, so each person connects it once. Until they do, Amplitude calls fail while the rest of the gateway keeps working.

    From then on, Amplitude's tools appear in Claude, limited to what the person's access allows, and every call lands in the gateway's tool logs.

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with Amplitude

Ask a usage question in plain words

Ask how many users completed checkout last week, and Claude runs the query and renders a chart, with a link to open and edit it in Amplitude.

query_datasetrender_chart

Summarize themes in customer feedback

Pull the grouped themes from customer feedback, then read the individual comments behind the biggest one before a planning meeting or a customer call.

get_feedback_insightsget_feedback_mentions

Find the dashboard someone already built

Before asking an analyst, search Amplitude for existing dashboards and charts on the topic and have Claude walk you through the one that fits.

searchget_dashboard

Tools

44 tools

Each Amplitude tool can be allowed or denied per team and role at the MCP Gateway before Claude sees it.

get_charts

Retrieve full chart objects by their IDs using the chart service directly

save_chart_edits

Save temporary chart edits as permanent charts

get_cohorts

Get detailed information about specific cohorts by their IDs.

create_cohort

Create a new cohort with the provided definition and configuration.

get_context

Get information about the current user, organization, and list of accessible projects.

get_project_context

Get project-specific settings and configuration for a specific project.

See all 44 tools

Control

What Speakeasy can see and stop in Claude

The gateway covers every client the same way. The rest depends on what Claude exposes to Speakeasy.

Tool logs

Gateway

Every Amplitude call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Amplitude tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Amplitude can reject a tool request before it reaches the server, or withhold a result from Claude. MCP-scoped policies are enabled per organization.

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Does Claude see Amplitude projects I can't open?
No. Each person signs in with their own Amplitude account and keeps the project access and permissions that account already has. Speakeasy roles can also limit which Amplitude tools a team can call.
Can Speakeasy block a prompt in Claude before it reaches Amplitude?
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
How do Claude users get Amplitude?
An admin adds Amplitude from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the Amplitude tools their access allows.
Are Amplitude calls from Claude logged?
Yes. Amplitude calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Amplitude in other clients

AI everywhere.

Control here.