Amplitude MCP connector
The Amplitude connector lets Claude, ChatGPT, Cursor, Microsoft Copilot 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.
- Connects with an API key
- Free 14-day trial
- No credit card
List all Amplitude cohorts created this quarter.
Working in Amplitude with Elaichi
-
List all Amplitude cohorts
-
Get single Amplitude cohort by ID
-
Get single Amplitude cohort file by ID
How to connect Amplitude to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Amplitude MCP connector for 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.
Amplitude MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Amplitude MCP connector for 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. The plugin directory lives at chatgpt.com/plugins.
Amplitude MCP connector for 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.
Amplitude MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
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.
What teams do with Amplitude through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Amplitude is logged.
-
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.”
What connecting Amplitude gets you
6 screens from Elaichi, each doing one job for your Amplitude account.
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, Cursor or Microsoft Copilot
The agent
Ask about cohorts, get live answers.
Type a question in plain language and read it back from Amplitude records.
Copy the endpoint
AI apps
One Amplitude endpoint for every MCP client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, with no SDK or shared key.
Tool catalog
59 Amplitude tools, no custom code.
Events, cohorts, chart annotations and annotation categories are listed with their methods.
Toolboxes
Each team gets its own Amplitude toolbox.
Curate one toolbox for growth, another for product, and scope each to its team.
Shared connections
Teammates query Amplitude without touching credentials.
See who connected each Amplitude account and how many teams and members share it.
Audit log
Every Amplitude call is written down.
When, who, what happened, type and resource for each cohort and event call.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Amplitude digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
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 Jake Morgan
Approve Deny -
Post the digest
Amplitude
Queued
Automations
A schedule drafts your Amplitude digest.
Cohorts are fetched and grouped, an agent drafts, a person approves, Amplitude receives it.
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%
Collections and dashboards
Amplitude numbers computed, not asked for.
Four metrics, 14 days of events created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Amplitude
All three can connect Amplitude to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Amplitude tools | Allow or restrict single Amplitude tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Amplitude call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Amplitude tools for your AI agents
59 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.
Questions, answered
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, Microsoft Copilot, 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 restricting actions that change the taxonomy for a role 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 restricting the ability to create cohorts, edit categories or delete a taxonomy category. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
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, Microsoft Copilot and every other client at the same time.
Does the Amplitude MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Amplitude is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Amplitude?
Yes. Both let Claude, ChatGPT or Cursor use Amplitude. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Amplitude call.
How is Elaichi different from Composio for Amplitude?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Amplitude: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Amplitude in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot