# Amplitude [Health: Active]

**Category:** 👤 Customer Data Platforms  
**Repository:** https://github.com/pipeworx-io/mcp-amplitude  
**GitHub Stars:** 0  
**npm Downloads (last month):** 422  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/amplitude

## Description
Amplitude MCP Pack

## Tools
Capabilities this server exposes over MCP:

- **amp_get_events** — Get event counts and breakdowns for a date range (e.g., "2024-01-01" to "2024-01-31"). Returns frequency, user segments, and trends by event name.
- **amp_get_active_users** — Get active user counts by granularity (daily, weekly, or monthly) for a date range. Returns totals and trend data.
- **amp_get_retention** — Get user retention metrics for a cohort over time. Returns retention percentages by time period (e.g., day 1, day 7, day 30).
- **amp_user_search** — Search for users by ID or property (e.g., email, user_id). Returns matching profiles with properties, event history, and segments.
- **amp_get_user_activity** — Get recent event activity timeline for a specific user. Returns events with timestamps, properties, and interactions.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "amplitude": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-amplitude"]
  }
}
```

## Documentation

## 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.

_Full upstream README: https://allmcps.com/mcp/amplitude/readme_