Amplitude MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| amplitude-api-key | Yes | Your Amplitude API key | |
| amplitude-secret-key | Yes | Your Amplitude secret key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_eventsD | – |
| segment_eventsD | – |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.