Skip to main content
Back to the Amplitude MCP server

MCP Gateway · Claude Cowork

Amplitude icon

Connect Amplitude to Claude Cowork

Recurring reporting is a multi-step job: query, chart, save and lay out. In Cowork, Claude can run that whole sequence against Amplitude through the Speakeasy MCP Gateway, then write the result up as a notebook for the team. Agent hooks send each prompt to Speakeasy before the step runs, and Cowork's OTLP export ties every session to a person.

Category
Data & analytics
Tools
44
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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 Cowork 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. Claude Cowork connects to the Amplitude server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Amplitude from Claude Cowork

    The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Amplitude

Assemble the weekly metrics dashboard

Cowork queries each metric, saves the charts so they persist, and builds a dashboard with charts, rich text and a custom layout, ready for Monday's review.

query_datasetsave_chart_editscreate_dashboard

Write a findings notebook

Have Cowork pull the latest data from saved charts and write an interactive notebook that explains what changed, for readers who won't open the raw charts.

query_chartscreate_notebook

Gather AI analyses of replays

Collect results from Amplitude's AI agents that have already analyzed your dashboards or session replays, and combine them into one summary of issues worth fixing.

get_agent_results

Tools

44 tools

Each Amplitude tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Cowork

The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Can personal Claude accounts use Amplitude in Cowork?
Personal Claude accounts can't be governed in Cowork. Neither the device agent nor MDM reaches Cowork either, so the Claude-side plugin setup is what applies.
What does an Amplitude admin need to check first?
An Amplitude organization admin confirms the MCP server is allowed under Settings > Content Access > MCP, and enables Use MCP (read) on any custom roles. Use MCP (write) is only needed for roles that change content.
How do Claude Cowork users get Amplitude?
An admin adds Amplitude from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Amplitude tools their access allows.
Are Amplitude calls from Claude Cowork 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.