
Amplitude MCP Server
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.
README
Amplitude MCP Server
A Model Context Protocol (MCP) server for integrating Amplitude analytics into AI workflows. This server allows AI assistants like Claude to track events, page views, user signups, set user properties, and track revenue in Amplitude.
Version 1.0.1 Note: Tool names now include the amplitude_
prefix to prevent namespace collisions with other analytics MCP servers.
Table of Contents
- Features
- Installation
- Quick Start
- Detailed Usage
- Tool Reference
- Examples
- Troubleshooting
- Security Notes
- Contributing
- License
Features
- Track custom events in Amplitude
- Track page views with properties
- Track user signups and create user profiles
- Update existing user properties
- Track revenue and purchases
- Simple integration with Claude Desktop and other MCP clients
Installation
Prerequisites
- Node.js 16 or higher
- An Amplitude API key (get one by signing up at Amplitude)
NPM Installation (Recommended)
# Install globally
npm install -g amplitude-mcp-server
# Or use directly with npx
npx amplitude-mcp-server --api-key YOUR_AMPLITUDE_API_KEY
Manual Installation
# Clone the repository
git clone https://github.com/ciaraadkins/amplitude-mcp-server.git
cd amplitude-mcp-server
# Install dependencies
npm install
# Run the server
node index.js --api-key YOUR_AMPLITUDE_API_KEY
Quick Start
To start using the Amplitude MCP server with Claude Desktop:
-
Make sure Claude Desktop is installed on your machine (download from claude.ai/download)
-
Create or edit the Claude Desktop configuration file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
- Windows:
%AppData%\Claude\claude_desktop_config.json
- macOS:
-
Add the Amplitude MCP server configuration:
{
"mcpServers": {
"amplitude-analytics": {
"command": "npx",
"args": [
"-y",
"amplitude-mcp-server",
"--api-key",
"YOUR_AMPLITUDE_API_KEY"
]
}
}
}
- Restart Claude Desktop and start tracking analytics!
Detailed Usage
With Claude Desktop
After setting up the configuration file as shown in the Quick Start section, you can use the Amplitude analytics capabilities directly in your conversations with Claude.
Examples of prompts you can use:
- "Track a custom event in Amplitude named 'document_generated' for user 'user123'"
- "Track a page view for the pricing page in Amplitude"
- "Create a new user profile in Amplitude for John Doe with email john@example.com"
- "Update user profile information in Amplitude for user 'user123'"
- "Track a purchase of Product X for $49.99"
Claude will use the appropriate Amplitude MCP tool based on your request.
With Other MCP Clients
This server uses the standard Model Context Protocol and can be integrated with any MCP client:
-
Start the server:
npx amplitude-mcp-server --api-key YOUR_AMPLITUDE_API_KEY
-
Connect your MCP client to the server using stdio transport
-
The client can discover and use the available tools (track_event, track_pageview, track_signup, set_user_properties, track_revenue)
Tool Reference
The Amplitude MCP server provides the following tools:
amplitude_track_event
Tracks a custom event in Amplitude.
Parameters:
event_name
(string, required): The name of the event to trackuser_id
(string, optional): User identifierdevice_id
(string, optional): Device identifierproperties
(object, optional): Additional properties to track with the eventuser_properties
(object, optional): User properties to update with this event
Note: Either user_id
or device_id
must be provided.
Example:
{
"event_name": "button_clicked",
"user_id": "user123",
"properties": {
"button_id": "submit_form",
"page": "checkout"
},
"user_properties": {
"last_action": "form_submit"
}
}
amplitude_track_pageview
Tracks a page view event in Amplitude.
Parameters:
page_name
(string, required): The name of the page vieweduser_id
(string, optional): User identifierdevice_id
(string, optional): Device identifierproperties
(object, optional): Additional properties to track with the event
Note: Either user_id
or device_id
must be provided.
Example:
{
"page_name": "homepage",
"user_id": "user123",
"properties": {
"referrer": "google.com",
"duration": 120
}
}
amplitude_track_signup
Tracks a signup event and creates a user profile in Amplitude.
Parameters:
user_name
(string, required): User's full nameemail
(string, required): User's email addressplan
(string, optional): Signup plan. Defaults to 'free'
Example:
{
"user_name": "John Doe",
"email": "john@example.com",
"plan": "premium"
}
amplitude_set_user_properties
Updates a user's profile properties in Amplitude.
Parameters:
user_id
(string, required): User identifierproperties
(object, required): Profile properties to set
Example:
{
"user_id": "user123",
"properties": {
"name": "John Doe",
"email": "john@example.com",
"plan": "premium",
"company": "Acme Inc"
}
}
amplitude_track_revenue
Tracks a revenue event in Amplitude.
Parameters:
user_id
(string, required): User identifierproduct_id
(string, required): Identifier for the product purchasedprice
(number, required): Price of the item purchasedquantity
(number, optional): Quantity of items purchased. Defaults to 1revenue_type
(string, optional): Type of revenue (e.g., 'purchase', 'refund', 'subscription')
Example:
{
"user_id": "user123",
"product_id": "premium_plan",
"price": 49.99,
"quantity": 1,
"revenue_type": "subscription"
}
Examples
Here are some practical examples of using the Amplitude MCP server with Claude:
Tracking a Button Click
You: Can you track an event in Amplitude when a user clicks the submit button?
Claude: I'll track that event for you. Let me use the Amplitude analytics tool.
[Claude uses the amplitude_track_event tool with appropriate parameters]
Claude: I've successfully tracked the 'button_clicked' event in Amplitude with the properties you specified.
Creating a User Profile
You: Create a new user profile in Amplitude for Sarah Johnson who signed up with sarah@example.com on the premium plan.
Claude: I'll create that user profile in Amplitude.
[Claude uses the amplitude_track_signup tool with appropriate parameters]
Claude: I've successfully tracked the signup for Sarah Johnson and created a profile in Amplitude with the premium plan.
Tracking Revenue
You: Track a purchase of our premium plan for $99.99 by user12345.
Claude: I'll track that revenue event in Amplitude.
[Claude uses the amplitude_track_revenue tool with appropriate parameters]
Claude: I've successfully tracked revenue of $99.99 for the premium plan purchase by user12345.
Troubleshooting
Common Issues
-
Server not starting:
- Ensure you've provided a valid Amplitude API key
- Check that Node.js is installed and is version 16 or higher
-
Claude Desktop not showing Amplitude tools:
- Verify your claude_desktop_config.json file syntax
- Make sure you've restarted Claude Desktop after editing the config
- Check that the path to the server is correct
-
Events not appearing in Amplitude:
- Verify your Amplitude API key is correct
- Check your Amplitude project settings to ensure data is being received
- Events may take a few minutes to appear in the Amplitude interface
Debug Mode
To run the server in debug mode for more verbose logging:
npx amplitude-mcp-server --api-key YOUR_AMPLITUDE_API_KEY --debug
Security Notes
- Your Amplitude API key is stored in the Claude Desktop configuration file. Ensure this file has appropriate permissions
- Consider using environment variables for sensitive tokens in production environments
- This server does not implement rate limiting - consider adding additional security measures for production use
- Events are sent directly to Amplitude's API - review Amplitude's privacy policy for data handling practices
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature
) - Commit your changes (
git commit -m 'Add some amazing feature'
) - Push to the branch (
git push origin feature/amazing-feature
) - Open a Pull Request
License
This project is licensed under the MIT License - see the LICENSE file for details.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.