How do I use Amplitude MCP Server?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. 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

by silviorodrigues

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

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 query
- eventType (string): Type of event
- propertyFilters (array, optional): Filters for event properties
start (string): Start date in YYYYMMDD format
end (string): End date in YYYYMMDD format
interval (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_events
filters (array, optional): Additional filters for segmentation
- type (string): Filter type (property, event, user)
- propertyName (string, optional): Name of the property
- value (mixed, optional): Value to filter by
- op (string, optional): Operator for comparison
breakdowns (array, optional): Breakdown dimensions
- type (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-31

Development

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

License

MIT

Available Tools

2 tools

query_eventsD

ParametersJSON Schema

Name	Required	Description	Default
`events`	Yes
`start`	Yes
`end`	Yes
`interval`	No
`groupBy`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

segment_eventsD

ParametersJSON Schema

Name	Required	Description	Default
`events`	Yes
`start`	Yes
`end`	Yes
`interval`	No
`groupBy`	No
`filters`	No
`breakdowns`	No

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

2 tool updatesv0.0.2May 30, 2026
- First observedquery_events
- First observedsegment_events

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

D1.5/5.0

Scored 2026-05-30 19:35 across 2 tools

Disambiguation3/5

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.

Naming Consistency4/5

Both tools use a consistent snake_case verb_noun pattern ('query_events', 'segment_events'), which is clear and predictable.

Tool Count2/5

Only 2 tools is insufficient for a service like Amplitude, which typically offers a wide range of analytics operations. The surface feels too thin.

Completeness2/5

The set is severely incomplete for any meaningful analytics workflow. Missing CRUD operations for events, user properties, and other essential endpoints.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Related Servers

Related MCP Connectors

AmplitudeOAuth
com.amplitude
Search, access, and get insights on your Amplitude data
Monitoring Search Data Platforms
2
Agent-Native AnalyticsOAuth
io.github.BuilderIO
Agent-Native Amplitude/Mixpanel - connect data sources, prompt for charts
Data Visualization Product Management Data Platforms
14,698
PressoOAuth
now.presso
Connect e-commerce and marketing data to AI assistants via MCP.
E-commerce & Retail Marketing Data Platforms
22
Airbyte AgentsOAuth
io.github.airbytehq
Let AI agents query data and act across all your business apps via MCP.
Data Platforms AI & Machine Learning RAG Systems
2

Related MCP Servers

Amplitude MCP Server
Databases Research & Data
moonbirdai
A
license
Not graded
quality
D
maintenance
A 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.
Updated a year ago (2025-04-17 17:07 UTC)
5 npm
7
MIT
Amplitude MCP Server
Customer Data Platforms Research & Data
ciaraadkins
A
license
Not graded
quality
D
maintenance
Enables AI assistants to integrate Amplitude analytics for tracking events, page views, user signups, user properties, and revenue.
Updated a year ago (2025-04-17 14:36 UTC)
5 npm
MIT
mcp-amplitude
Customer Data Platforms Monitoring Search
pipeworx-io
A
license
Not graded
quality
C
maintenance
Enables querying Amplitude analytics data including events, active users, retention, and user profiles through natural language or direct tool calls.
Updated 19 days ago (2026-08-26 16:33 UTC)
6 npm
MIT
Google Analytics MCP Server
Search Monitoring
rinaldofesta
A
license
Not graded
quality
D
maintenance
Enables querying Google Analytics 4 data using natural language through MCP clients like Claude and Cursor, supporting 200+ dimensions and metrics for traffic, user behavior, and e-commerce analysis.
Updated a year ago (2025-07-15 14:18 UTC)
MIT

Amplitude MCP Server

Overview

Installation

Required Credentials

Available Tools

1. query_events

2. segment_events

Available Resources

amplitude_events

Development

Project Structure

License

Available Tools

TDQS

TDQS

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Amplitude MCP Server

Amplitude MCP Server

mcp-amplitude

Google Analytics MCP Server