Analytics
Amplitude MCP connector
The Amplitude connector lets Claude, ChatGPT, Cursor and other AI clients work with your Amplitude cohorts, chart annotations, releases, event taxonomy and user properties through one governed endpoint, with every action tied to a named person.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Amplitude to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Amplitude once
-
Open Connections, choose Add connection, and pick Amplitude.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste an Amplitude API key. One person generates a token in Amplitude and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Amplitude to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Amplitude to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Amplitude to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Amplitude to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Amplitude through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Product
Mark a release on every chart
After a feature ships, ask the agent to create the release in Amplitude and add a chart annotation so the whole team sees why retention moved that week.
-
Marketing
Build a cohort for the next campaign
Describe the audience in plain language, such as users who completed onboarding but never invited a teammate, and have the agent create the cohort in Amplitude ready for export to your email tool.
-
Growth
Record attribution from offline touchpoints
When a lead comes in from an event booth or a partner referral, the agent records the attribution and the conversion event in Amplitude so paid and organic channels are compared fairly.
-
Analytics
Keep the event taxonomy tidy
Ask which event types exist, group them into taxonomy categories, rename a category that no longer fits, and remove an empty one, all without opening the taxonomy screen.
-
Customer success
Update an account's profile after a call
When a customer upgrades or changes owner, the agent updates their user properties and the group properties for the account in Amplitude so segments and dashboards reflect the change the same day.
-
Engineering
Annotate a chart after an incident
Once an outage is resolved, the agent adds a dated annotation to the affected Amplitude chart under an incidents category so nobody mistakes the dip for a product problem later.
Try asking
- “List all Amplitude cohorts created this quarter.”
- “Which chart annotations landed on last week's release?”
- “Summarize event volume by annotation category.”
AI tools
Amplitude tools for your AI agents
58 tools are ready to call through Elaichi's MCP endpoint the moment you connect Amplitude, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Amplitude gets you
6 screens from the product, each doing one job for your Amplitude account.
The agent
Ask about cohorts, get live answers.
Type a question in plain language and read it back from Amplitude records.
- events
- cohorts
- chart annotations
- annotation categories
Ask Elaichi to work across your apps.
List all Amplitude cohorts created this quarter.
Which chart annotations landed on last week's release?
Summarize event volume by annotation category.
Also runs in Claude, ChatGPT or Cursor
MCP clients
One Amplitude endpoint for every MCP client.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK or shared key.
Copy the endpoint
Tool catalog
58 Amplitude tools, no custom code.
Events, cohorts, chart annotations and annotation categories are listed with their methods.
- Create a Amplitude event
- Create a Amplitude batch event
- Create a Amplitude identify
- Create a Amplitude group identify
Toolboxes
Each team gets its own Amplitude toolbox.
Curate one toolbox for growth, another for product, and scope each to its team.
- Growth
- Product
- Data
- Marketing
Shared connections
Teammates query Amplitude without touching credentials.
See who connected each Amplitude account and how many teams and members share it.
- Growth EMEA
- Product Core
- Marketing
- Data Platform
Audit log
Every Amplitude call is written down.
When, who, what happened, type and resource for each cohort and event call.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule drafts your Amplitude digest.
Cohorts are fetched and grouped, an agent drafts, a person approves, Amplitude receives it.
Amplitude digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch events
Amplitude
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Amplitude
Queued
Collections and dashboards
Amplitude numbers computed, not asked for.
Four metrics, 14 days of events created and a team breakdown, refreshed on schedule.
Amplitude health
Refreshed 4 minutes ago · every 15 minutes · from the events collection
Events
1,284 ↓ 12%
Cohorts
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Events created
Last 14 days
By team
Share of activity
Growth EMEA 34%
Product Core 27%
Marketing 21%
Data Platform 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Amplitude to Claude?
Connecting Amplitude to Claude takes two steps. First, connect Amplitude in Elaichi by pasting the API key from your Amplitude project settings, there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the Elaichi endpoint, https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on it can work with your Amplitude cohorts, annotations and releases.
Does Amplitude work with ChatGPT and Cursor as well as Claude?
Yes. Once Amplitude is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi agent. You connect Amplitude once and every client picks it up, with the same permissions and the same audit log.
What can an AI agent actually do with my Amplitude data?
With Amplitude connected, an agent can list your cohorts and open any one of them, create a new cohort from a description, add annotations to charts and organize them into categories, mark a release, check which exports exist, and tidy the event taxonomy. It can also record events, user properties, group properties and attribution in Amplitude when something happens outside the product, such as a signed contract or an event booth visit. Because Amplitude has a lot of possible actions, short concrete asks such as 'annotate the signup chart for today's release' work better than long paragraphs.
Does connecting Amplitude give the AI access to every project?
No. The agent can only reach what the Amplitude API key used for the connection can reach, which in Amplitude means the project that key belongs to, and every request runs under the Elaichi identity of the person who asked. Elaichi can narrow that further, for example by hiding actions that change the taxonomy from a team that only reads cohorts, but it can never grant anything the Amplitude key itself does not allow.
Can I stop an agent from deleting or changing things in Amplitude?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Amplitude cohorts and annotations while blocking the ability to create cohorts, edit categories or delete a taxonomy category. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt, however it is worded, can reach it.
What happens to an Amplitude connection when someone leaves?
When you offboard a person in Elaichi, their access to Amplitude through every AI client ends at once, and there is no API key on their laptop to chase. If they had shared an Amplitude connection with a team, that connection keeps working for everyone else. If you ever want to remove Amplitude entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.
Put Amplitude in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.