# 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.

Source: https://elaichi.ai/connectors/amplitudescim/

## Facts

| | |
| --- | --- |
| Application | Amplitude SCIM |
| Category | Analytics |
| AI tools | 11 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Amplitude SCIM is connected

- 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 dan@acme.com belong to?

## Connect Amplitude SCIM in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Amplitude SCIM.
2. Optionally set Share with, then press Connect.
3. Paste an Amplitude SCIM API key. One person generates a token in Amplitude SCIM and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Amplitude SCIM tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Amplitude SCIM MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Amplitude SCIM MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

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.
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.

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

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Amplitude SCIM tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Amplitude SCIM through Elaichi

### Provision a new hire's Amplitude account

IT. 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.

### Offboard a leaver from Amplitude

IT. Find the departing person's Amplitude user, remove it, and confirm they no longer appear in any group.

### Audit who holds an Amplitude seat

Security. List every Amplitude user and group and ask which accounts do not match the current roster, then act on the stragglers.

### Set up a group for a new squad

Data. Create an Amplitude group for a new analytics squad and add the analysts who should be in it, all in one ask.

### Fix a name or email after a change

People Ops. Update an Amplitude user's details after a name change, a new email domain or a team move, without digging through settings.

### Pull evidence for an access review

Compliance. Ask for the full list of Amplitude users and their groups and get a plain summary you can paste into the review.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Amplitude SCIM connection?

Yes. One person connects Amplitude SCIM in Elaichi and shares it with a team, and nobody else ever handles the API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every user or group change in Amplitude.

### 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.

## All 11 Amplitude SCIM tools

Every tool below is callable through https://api.elaichi.ai/mcp once Amplitude SCIM is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Amplitude SCIM users** (List). List users in the Amplitude organization via SCIM, including pending (invited) and joined users. Supports SCIM filter, e.g. userName eq "jane@acme.com". Returns: id (email), userName, name, emails, active.
- **Get single Amplitude SCIM user by ID** (Get). Get an Amplitude user by id; the SCIM id is the user's email (not case sensitive). Returns: id, userName, name, emails, active, groups. Required: id.
- **Create a Amplitude SCIM user** (Create). Invite (create) a user in Amplitude via SCIM; Amplitude emails an invitation. id and userName must be the email and the user must not already exist or be invited. Groups are ignored here; use groups update to add members. Required: schemas, id, userName, name.
- **Update a Amplitude SCIM user by ID** (Update). Replace an Amplitude user via SCIM PUT (send the full user). Set active false to remove the user from the organization or revoke a pending invite. The email cannot be changed. Required: id (email), schemas, userName, name.
- **Amplitude SCIM users partial update** (Update). Partially update an Amplitude user via SCIM PATCH, e.g. {"op":"replace","path":"active","value":false} to remove the user. Required: user_id (email), schemas, Operations.
- **Delete a Amplitude SCIM user by ID** (Delete). Delete an Amplitude user via SCIM (revokes a pending invite). Required: id (email).
- **List all Amplitude SCIM groups** (List). List Amplitude permission groups via SCIM. Supports SCIM filter. Returns: id, displayName, members (email, display).
- **Get single Amplitude SCIM group by ID** (Get). Get an Amplitude permission group by numeric id. Returns: id, displayName, members, meta. Required: id.
- **Create a Amplitude SCIM group** (Create). Create an Amplitude permission group via SCIM with optional members (emails). Members not yet in the organization are invited with minimum permissions. Required: schemas, displayName.
- **Update a Amplitude SCIM group by ID** (Update). Add or remove group members via SCIM PATCH: {"op":"add","path":"members","value":[{"value":"&lt;email&gt;"}]} or op remove. Required: id, schemas, Operations.
- **Delete a Amplitude SCIM group by ID** (Delete). Delete an Amplitude permission group. Required: id.
