Amplitude MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Amplitude MCP Server show me user login events for last week"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Amplitude MCP Server
A Model Context Protocol (MCP) server for Amplitude Analytics API, providing tools and resources for querying and segmenting event data.
Overview
This MCP server enables AI assistants and other MCP clients to interact with the Amplitude Analytics API, allowing them to:
Query event data with filters
Perform advanced segmentation with breakdowns
Access event data through structured resources
Related MCP server: Amplitude MCP Server
Installation
{
"mcpServers": {
"amplitude": {
"command": "npx",
"args": [
"-y",
"amplitude-mcp",
"--amplitude-api-key=YOUR_API_KEY",
"--amplitude-secret-key=YOUR_SECRET_KEY"
]
}
}
}Required Credentials
Amplitude API credentials must be provided using command line arguments:
--amplitude-api-key: Your Amplitude API key (required)--amplitude-secret-key: Your Amplitude secret key (required)
Available Tools
1. query_events
Basic event querying with filters.
Parameters:
events(array): Array of events to queryeventType(string): Type of eventpropertyFilters(array, optional): Filters for event properties
start(string): Start date in YYYYMMDD formatend(string): End date in YYYYMMDD formatinterval(string, optional): Grouping interval (day, week, month)groupBy(string, optional): Grouping dimension
Example:
{
"events": [
{
"eventType": "user_login",
"propertyFilters": [
{
"propertyName": "device_type",
"value": "mobile",
"op": "is"
}
]
}
],
"start": "2023-01-01",
"end": "2023-01-31",
"interval": "day"
}2. segment_events
Advanced event segmentation with breakdowns.
Parameters:
All parameters from
query_eventsfilters(array, optional): Additional filters for segmentationtype(string): Filter type (property, event, user)propertyName(string, optional): Name of the propertyvalue(mixed, optional): Value to filter byop(string, optional): Operator for comparison
breakdowns(array, optional): Breakdown dimensionstype(string): Breakdown type (event, user)propertyName(string): Name of the property to break down by
Example:
{
"events": [
{
"eventType": "purchase"
}
],
"start": "2023-01-01",
"end": "2023-01-31",
"interval": "week",
"filters": [
{
"type": "user",
"propertyName": "country",
"value": "US",
"op": "is"
}
],
"breakdowns": [
{
"type": "user",
"propertyName": "device_type"
}
]
}Available Resources
amplitude_events
Access event data for a specific event type and date range.
URI Format:
amplitude://events/{eventType}/{start}/{end}Example:
amplitude://events/user_login/2023-01-01/2023-01-31Development
Project Structure
amplitude-mcp/
├── src/
│ ├── index.ts # Main entry point with MCP server setup
│ ├── services/
│ │ └── amplitude.service.ts # Amplitude API service implementation
│ ├── resources/
│ │ └── events.ts # Event data resources
│ ├── types/
│ │ └── amplitude.ts # Amplitude API types
│ └── utils/
│ └── config.ts # Configuration and credential handling
├── bin/
│ └── cli.js # CLI entry point
├── dist/ # Compiled JavaScript files
├── package.json
└── tsconfig.jsonLicense
MIT
Available Tools
2 toolsquery_eventsD
Inputs: events (required), start (required), end (required), interval, +1 more.
segment_eventsD
Inputs: events (required), start (required), end (required), interval, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The tool names suggest different operations ('query' vs 'segment'), but the lack of descriptions prevents clear disambiguation. An agent might still select incorrectly without more context.
Both tools use a consistent snake_case verb_noun pattern ('query_events', 'segment_events'), which is clear and predictable.
Only 2 tools is insufficient for a service like Amplitude, which typically offers a wide range of analytics operations. The surface feels too thin.
The set is severely incomplete for any meaningful analytics workflow. Missing CRUD operations for events, user properties, and other essential endpoints.
Related MCP Connectors
Search, access, and get insights on your Amplitude data
Agent-Native Amplitude/Mixpanel - connect data sources, prompt for charts
Connect e-commerce and marketing data to AI assistants via MCP.
Analytics your AI agent can actually use. Track, experiment, and optimize via MCP.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that enables AI assistants like Claude to track events, page views, user signups, set user properties, and track revenue in Amplitude analytics.14 npm7MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to integrate Amplitude analytics for tracking events, page views, user signups, user properties, and revenue.14 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables querying Amplitude analytics data including events, active users, retention, and user profiles through natural language or direct tool calls.92 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI to interact with ThinkingData analytics through a read-only MCP service, supporting event/property queries, event analysis, retention analysis, and safe SQL execution.Apache 2.0