Amplitude SCIM MCP connector
The Amplitude SCIM connector brings Amplitude users and groups into Elaichi, so Claude, ChatGPT, Cursor and Microsoft Copilot can list, create, update and remove Amplitude accounts, inside each person's own access and with every change logged.
- Connects with an API key
- Free 14-day trial
- No credit card
List every Amplitude user who is not in any group
Working in Amplitude SCIM with Elaichi
-
List all Amplitude SCIM users
-
Get single Amplitude SCIM user by ID
-
List all Amplitude SCIM groups
How to connect Amplitude SCIM to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Amplitude SCIM 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 SCIM 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 SCIM 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 SCIM 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 SCIM 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 SCIM 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 SCIM 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 SCIM is logged.
-
IT
Provision a new hire's Amplitude account
Create the Amplitude user on day one and put them in the right groups, without opening the admin console or waiting for a ticket to be picked up.
-
IT
Offboard a leaver from Amplitude
Find the departing person's Amplitude user, remove it, and confirm they no longer appear in any group.
-
Security
Audit who holds an Amplitude seat
List every Amplitude user and group and ask which accounts do not match the current roster, then act on the stragglers.
-
Data
Set up a group for a new squad
Create an Amplitude group for a new analytics squad and add the analysts who should be in it, all in one ask.
-
People Ops
Fix a name or email after a change
Update an Amplitude user's details after a name change, a new email domain or a team move, without digging through settings.
-
Compliance
Pull evidence for an access review
Ask for the full list of Amplitude users and their groups and get a plain summary you can paste into the review.
Try asking
- “List every Amplitude user who is not in any group”
- “Create an Amplitude user for Priya Shah and add her to Growth”
- “Which Amplitude groups does [email protected] belong to?”
What connecting Amplitude SCIM gets you
6 screens from Elaichi, each doing one job for your Amplitude SCIM account.
Ask Elaichi to work across your apps.
List every Amplitude user who is not in any group
Create an Amplitude user for Priya Shah and add her to Growth
Which Amplitude groups does [email protected] belong to?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask who has Amplitude access, in plain words.
Three starter prompts pull live Amplitude SCIM users and groups into a conversation.
Copy the endpoint
AI apps
One endpoint, every client, no shared API key.
Claude, ChatGPT and Cursor reach Amplitude SCIM through one governed org endpoint, no SDK required.
Tool catalog
11 Amplitude SCIM tools cover users and groups.
List, create, update and delete users and groups with no custom code written.
Toolboxes
Every team gets its own Amplitude SCIM toolbox.
IT provisions accounts, Security reviews seats, each from a toolbox scoped to them.
Shared connections
Teammates provision through one connection, credential unseen.
The table shows who connected Amplitude SCIM and which teams and members it is shared with.
Audit log
Every user and group change names its author.
When, who, what happened, type and resource, logged for each Amplitude SCIM 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. Workflows, collections and live dashboards come with the Black plan.
Amplitude SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Amplitude SCIM
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 SCIM
Queued
Workflows
A schedule starts the Amplitude access review.
Users are fetched, grouped, drafted into a digest, approved by a person, then posted back.
Amplitude SCIM health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Groups
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
IT 34%
Security 27%
People Ops 21%
Data 18%
Collections and dashboards
Amplitude seat counts, computed without a model.
Four metrics, fourteen days of users created and a breakdown by team, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Amplitude SCIM
All three can connect Amplitude SCIM 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 SCIM tools | Allow or restrict single Amplitude SCIM 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 SCIM 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 SCIM tools for your AI agents
11 tools are ready to call through Elaichi's MCP endpoint the moment you connect Amplitude SCIM, 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 SCIM to Claude?
Two steps. First connect Amplitude SCIM in Elaichi, which only asks you to paste the API key from your Amplitude admin settings, with no OAuth application to register and no client ID or secret to generate. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and Amplitude users and groups are available in the conversation.
Does Amplitude SCIM work with ChatGPT and Cursor as well as Claude?
Yes. Once Amplitude SCIM is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Amplitude SCIM once and every client picks it up.
What can an AI agent actually do with my Amplitude SCIM data?
With Amplitude SCIM connected, an agent can list every Amplitude user and group, look up one person, create a user for a new hire, update a name or email, add or change groups, and remove a user who has left. Short, concrete asks work best, such as "add Priya to the Growth group" rather than a long paragraph of instructions.
Does connecting Amplitude SCIM give the AI every user and group in my Amplitude organization?
No. Access follows the person who signed in, so an agent working through Amplitude SCIM can only see and change the users and groups that person's API key is allowed to manage. Elaichi can narrow that further with roles and restrictions, and it never widens it.
Can I stop an agent from deleting or changing things in Amplitude SCIM?
Yes. Restrictions in Elaichi work per action, so you can allow listing Amplitude users while restricting creating, updating or deleting them, on a role or on one person. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to an Amplitude SCIM connection when someone leaves?
Offboarding that person in Elaichi ends their access to Amplitude SCIM at once. A shared Amplitude SCIM connection keeps working for everyone else on the team. If you disconnect Amplitude SCIM in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.
Does the Amplitude SCIM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Amplitude SCIM 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 SCIM?
Yes. Both let Claude, ChatGPT or Cursor use Amplitude SCIM. 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 SCIM call.
How is Elaichi different from Composio for Amplitude SCIM?
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 SCIM: 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 SCIM 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