Log inSubmit server
Amplitude logo

Amplitude

Queries Amplitude event, user, activity, active-user, and retention data through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Amplitude

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "amplitude": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-amplitude"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

We couldn’t confirm it starts correctly

The install command started, but didn't respond the way we expected when we tried to talk to it.

npx -y @pipeworx/mcp-amplitude

initialize succeeded but no response to tools/list.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1d ago.

Overview

The Amplitude MCP server exposes tools for querying Amplitude analytics and user data through MCP. It supports event trends, active-user counts, cohort retention, user searches, and individual activity timelines. Connect through the Pipeworx gateway over HTTP or run the package locally over stdio. Use it when an AI client needs to inspect product usage or user behavior without building separate Amplitude query logic.

Use cases

  • Analyze event trends across a date range
  • Measure daily, weekly, or monthly active users
  • Compare retention across cohort periods
  • Search for users by ID or property
  • Review a user's recent event activity

Key features

  • Event counts and trend breakdowns
  • Daily, weekly, and monthly active-user metrics
  • Cohort retention percentages
  • User search by identifier or property
  • User activity timelines

Tools5

What Amplitude lets your agent do. Expand a tool for its parameters.

Self-reported~180 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

6/6 checks healthy over the last 47d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 16d ago via OSV.dev · @pipeworx/mcp-amplitude (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads422Package downloads in the last 30 days.
Last commit5d agoMost recent push to the default branch.
Install checkInconclusiveStarted but did not complete the MCP handshake in our test.
Tools exposed5Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Amplitude works

What Amplitude MCP server does

The Amplitude MCP server provides five MCP tools for analyzing product and user data. It can summarize event activity over a selected date range, measure active users, calculate cohort retention, find user profiles, and inspect a specific user's recent event timeline.

The tools are oriented toward questions such as which events increased during a period, how many daily, weekly, or monthly active users a product had, how a cohort retained users on day 1 or day 30, or what actions appear in an individual user's recent history.

How it works

The package can be reached in two ways. A hosted connection uses the Pipeworx Amplitude endpoint at https://gateway.pipeworx.io/amplitude/mcp. That endpoint lists the Amplitude tools together with shared Pipeworx meta-tools. The shared tools can route broader questions through the Pipeworx catalog, while direct calls remain available for the pack's listed tools.

A local installation runs as an MCP process over standard input and output. The local process exposes only the five Amplitude tools and does not add the gateway's shared meta-tools or cross-catalog routing. Both modes use MCP operations such as initialization, tool discovery, and tool calls.

Setup and configuration

For a hosted connection, add the Amplitude endpoint as an MCP server in a compatible client. A full Pipeworx endpoint is also available when the client should list tools from all supported packs directly. The pack endpoint and full gateway use the same Pipeworx infrastructure; the difference is which tools are listed directly.

For local use, run the @pipeworx/mcp-amplitude package with npx -y and configure the command in the client. This mode does not require a Pipeworx account or a gateway round trip.

Tools and capabilities

  • amp_get_events returns event counts and breakdowns for a date range, including frequency, user segments, and trends grouped by event name.
  • amp_get_active_users reports active-user totals for daily, weekly, or monthly granularity and includes trend data.
  • amp_get_retention returns cohort retention percentages across time periods such as day 1, day 7, and day 30.
  • amp_user_search finds users by an identifier or property, including examples such as email and user_id. Results can include profiles, properties, event history, and segments.
  • amp_get_user_activity returns a recent activity timeline for a specific user, with event timestamps, properties, and interactions.

Limitations and notes

The Amplitude MCP server does not provide a standalone API-key-free HTTP example: callers must supply their own _apiKey for the pack's tools. Gateway connections expose additional shared schemas beyond the five pack tools, so the tool count shown by a client may be larger than the pack list. The local stdio mode avoids those shared tools but also cannot use Pipeworx's cross-catalog ask_pipeworx routing.

Validate those details against the tool schemas or the linked documentation before relying on them in production workflows.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Amplitude

Amplitude is an MCP server that connects AI clients to Amplitude data through Pipeworx. Its main tools retrieve event trends, active-user counts, retention metrics, user profiles, and recent activity timelines. It can run through the Pipeworx gateway over HTTP or locally as a stdio package.

Run `npx -y @pipeworx/mcp-amplitude` and register that command as an MCP server in your client. This local mode requires no Pipeworx account and communicates over stdin/stdout.

Yes, Amplitude works with Cursor through the hosted MCP endpoint or the local stdio package. Add `https://gateway.pipeworx.io/amplitude/mcp` as the server URL, or configure Cursor to run the package with `npx`.

Yes, tool calls require your own Amplitude API key supplied through the `_apiKey` argument.

Related MCP servers

All in Customer Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAmplitude AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/amplitude?style=directory)](https://allmcps.com/mcp/amplitude)
HTML Embed
<a href="https://allmcps.com/mcp/amplitude"><img src="https://allmcps.com/api/badge/amplitude?style=directory" alt="Amplitude on AllMCPs" /></a>