Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the Amplitude in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
Summary
Let your AI read your Amplitude product analytics: event trends, funnels, retention, active and new users, revenue LTV, sessions, saved charts, cohorts, user lookups and the tracking plan, and add chart annotations. US and EU data centers.
Try asking
Example prompts for Amplitude
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Amplitude, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
Amplitude + Cursor
Let your AI read your Amplitude product analytics: event trends, funnels, retention, active and new users, revenue LTV, sessions, saved charts, cohorts, user lookups and the tracking plan, and add chart annotations. US and EU data centers.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
AMPLITUDE_API_HOST, AMPLITUDE_API_KEY, AMPLITUDE_SECRET_KEY
Step 1 — Get credentials
- You need the Manager or Admin role in the Amplitude project. Select Settings (lower left), then Projects, and pick the project. Each project has its own keys, so one connector reads one project.
- On the project's General tab, select Manage next to API Key and copy the key into
AMPLITUDE_API_KEY. - Select Manage next to Secret Key and generate a new secret key for AnythingMCP. Amplitude shows a secret key only once, when it is generated, so paste it into
AMPLITUDE_SECRET_KEYstraight away. A project can have several secret keys. - Set
AMPLITUDE_API_HOSTto the project's data center:https://amplitude.comfor the default (US) data center,https://analytics.eu.amplitude.comfor an EU project (its app runs onapp.eu.amplitude.com). Keys of an EU project are refused on the US host and the other way round.analytics.amplitude.comis the web app, not the API. - Install the connector and run
amplitude_list_eventsto see the exact event names your project tracks.
Who sees what: the secret key reads every event and user of the project. Share the MCP server only with people allowed to see that data.
What it reads: event trends with filters and group bys, funnels, retention, active and new users (also live, in 5-minute steps), revenue LTV, session length and sessions per user, user composition, the results of charts saved in Amplitude (found by the id after /chart/ in the chart's address), behavioral cohorts, user lookups with a user's recent events, and the tracking plan (event types, event and user properties, categories). Dates are whole days in the project's time zone. The cohort list needs the Behavioral Cohorts add-on on Growth or Enterprise.
Limits: Amplitude's limits apply per project and are shared with every other integration. The Dashboard REST API runs at most 5 requests at the same time and has a query cost budget of 1,000 per 5 minutes and 108,000 per hour. A query costs the days in the range times the conditions (segments and filters; each group by counts 4) times the chart cost (segmentation 1 per event, funnels 2 per step, retention 8, sessions 4, everything else 1). User search and user activity have their own limit of 10 at the same time and 360 per hour, and the tracking plan allows 7,200 reads per hour. Above a limit Amplitude answers 429: the AI waits, and shortens the range or drops group bys when the cost budget is the problem. One query with a group by replaces many day-by-day or user-by-user queries.
Personal data: amplitude_search_users and amplitude_get_user_activity return a user's profile and events. The AI uses them for the user you ask about.
Confirm first: an annotation without a chart shows on every chart of the project for every member, so the AI confirms the label, time and scope with you before amplitude_create_annotation. amplitude_delete_annotation is switched off at install.
Common errors: 403 "Invalid API Key": the key or secret is wrong, belongs to another project, or the project lives in the other data center (check AMPLITUDE_API_HOST). 401: one of the two keys is missing. 400: a parameter or the JSON of an event or segment is invalid, or a saved chart belongs to another project. 404 on amplitude_get_chart_results: there is no saved chart with that id. 429: a concurrency, hourly or cost limit is reached, and Amplitude says which.
The connector does not send events into Amplitude, export raw event files, download or upload cohorts, delete users for privacy requests, or cover Experiment, Session Replay or user management.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Cursor
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Cursor reads MCP servers from ~/.cursor/mcp.json. Add this entry:
{
"mcpServers": {
"anythingmcp": {
"url": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
"headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
}
}
}
- Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of
YOUR_MCP_API_KEY. - Save the file and restart Cursor.
- Open Cursor → Settings → MCP and check that
anythingmcpis listed and connected. - Start chatting: the agent can now call the
Amplitudetools.
Available tools
| Tool | What it does |
|---|---|
amplitude_list_events | List the project's visible event types with this week's totals, as event_type, display name, weekly_totals and the hidden and inactive… |
amplitude_get_event_segmentation | Event Segmentation: count one event (or compare two) per day, week or month, optionally filtered by segments and grouped by a property |
amplitude_get_funnel | Funnel Analysis: conversion through two or more events in order |
amplitude_get_retention | Retention Analysis: how many users who did a starting event come back with a return event, per day, week or month after |
amplitude_get_active_users | Count active or new users per day, week or month, optionally segmented and grouped by a property |
amplitude_get_realtime_active_users | Active users in 5-minute steps for today and yesterday, for a live view |
amplitude_get_revenue_ltv | Revenue lifetime value of new users per start date: average revenue per user, per paying user, total revenue or paying users after 1 to 90… |
amplitude_get_session_length_distribution | Number of sessions per session length bucket over a date range |
amplitude_get_average_session_length | Average session length in seconds for each day of a date range |
amplitude_get_sessions_per_user | Average number of sessions per user for each day of a date range |
amplitude_get_user_composition | User composition: how many distinct users had each value of one user property in a date range (e.g. users per country, platform or app… |
amplitude_get_chart_results | Run a chart saved in Amplitude and return its results, using the chart's saved definition (events, filters, date range) |
amplitude_list_cohorts | List the project's discoverable behavioral cohorts with id, name, description, size, owners, last computed time and archived or published… |
amplitude_search_users | Find users by Amplitude ID, device ID, user ID or the start of a user ID |
amplitude_get_user_activity | One user's summary (userData: first and last seen, event and session counts, revenue, platform, location, user properties) and their most… |
amplitude_list_event_types | List the event types planned in the project's tracking plan (Amplitude Data) with category, display name, description, active flag, tags… |
amplitude_get_event_type | Get one planned event type by its exact name: category, display name, description, active and hidden flags, tags and owner |
amplitude_list_event_properties | List the event properties in the tracking plan: for one event type when event_type is given, otherwise the shared event properties |
amplitude_list_user_properties | List the project's user properties with description, type, enum values, array flag and classifications |
amplitude_list_event_categories | List the event categories of the tracking plan (id and name) |
amplitude_list_annotations | List the chart annotations of the project (releases, campaigns, incidents marked on charts): id, label, details, start and end, category… |
amplitude_create_annotation | Add an annotation (e.g. a release or campaign) at a point or range in time |
amplitude_delete_annotation | Delete a chart annotation by id; it disappears from every chart for every member and cannot be restored |
Example prompts
- "How many users did Sign Up each week over the last three months, grouped by country?"
- "Show me the funnel from Sign Up to Create Project to Invite Teammate for September and the step where most users drop off."
- "Of the new users who started in August, how many came back in each of the following eight weeks?"
- "Add an annotation for the pricing page relaunch on 1 October to every chart, and show me the label and date before you save it."
FAQ
Does Cursor support custom MCP servers on the free tier? Yes, MCP is available on Hobby, Pro and Business plans.
Next steps
Was this guide helpful?