# Mixpanel SCIM MCP connector

The Mixpanel SCIM connector brings Mixpanel users and groups into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client can list, create, update and remove them inside each person's own access, with every change logged.

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

## Facts

| | |
| --- | --- |
| Application | Mixpanel SCIM |
| Category | Analytics |
| AI tools | 13 |
| 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 Mixpanel SCIM is connected

- List every Mixpanel SCIM user who is not in any group
- Add Priya Shah to the Growth analytics group
- Show me all groups and how many members each has

## Connect Mixpanel SCIM in Elaichi

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

1. Open Connections, choose Add connection, and pick Mixpanel SCIM.
2. Optionally set Share with, then press Connect.
3. Paste a Mixpanel SCIM API key. One person generates a token in Mixpanel 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 Mixpanel SCIM tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

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

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

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

## Mixpanel 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 Mixpanel 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 Mixpanel 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 Mixpanel SCIM through Elaichi

### Set up a new hire in Mixpanel

IT. Create the Mixpanel user and add them to the right groups from one request, the same day their laptop arrives.

### Remove access the moment someone leaves

Security. Find the person's Mixpanel account, delete it, and confirm it is gone before the exit interview is over.

### Check who still has a Mixpanel account

People Ops. Pull the full user list and compare it to the current staff roster ahead of the quarterly review.

### Move analysts between project groups

Product analytics. Update group membership when someone changes teams, without opening the Mixpanel admin console.

### Count seats before the renewal call

Finance. List every Mixpanel user and group so the seat number going into the renewal conversation is current, not a guess.

### Answer an access review in minutes

Compliance. List users and groups, then point to Elaichi's audit log to show who created or removed each account and when.

## Elaichi vs Zapier MCP vs Composio for Mixpanel SCIM

All three can connect Mixpanel 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 Mixpanel SCIM tools | Allow or restrict single Mixpanel 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 Mixpanel 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 Mixpanel SCIM to Claude?

Connect Mixpanel SCIM in Elaichi first: paste the SCIM API key from Mixpanel's organization settings and save. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Mixpanel SCIM is available in the chat.

### Does Mixpanel SCIM work with ChatGPT and Cursor as well as Claude?

Yes. Once Mixpanel SCIM 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. Connect it once and every client sees it.

### What can an AI agent actually do with my Mixpanel SCIM data?

It can list the people and groups in your Mixpanel organization, look up one person, create a new account, update someone's details or group membership, and remove an account. It can also read the SCIM configuration, schemas and resource types Mixpanel exposes. Short, concrete asks such as add Priya to the Growth group work better than long sentences.

### Does connecting Mixpanel SCIM give the AI control of my whole Mixpanel organization?

No. Every call through Mixpanel SCIM runs as the person who signed in to Elaichi, using the connection they were given, and nothing more. Elaichi can narrow that access for a role or a person, for example read only, and it can never widen it beyond what the Mixpanel SCIM key allows.

### Can my team share one Mixpanel SCIM connection?

Yes. One Mixpanel admin connects Mixpanel SCIM with the API key and shares the connection with the IT or security team in Elaichi. Nobody else ever sees or handles the key, and because each person signs in to Elaichi as themselves, the audit log still names who created, changed or removed each Mixpanel user.

### Can I stop an agent from deleting or changing users in Mixpanel SCIM?

Yes. In Elaichi you can restrict any single action in Mixpanel SCIM, such as deleting a user or changing a group, for a role or for 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 a Mixpanel SCIM connection when someone leaves?

Offboarding someone in Elaichi ends their access to the Mixpanel SCIM connection at once, in every client they used. If the connection was shared, it keeps working for everyone else. If you disconnect Mixpanel SCIM in Elaichi, it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client in one step.

### Does the Mixpanel SCIM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Mixpanel 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 Mixpanel SCIM?

Yes. Both let Claude, ChatGPT or Cursor use Mixpanel 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 Mixpanel SCIM call.

### How is Elaichi different from Composio for Mixpanel 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 Mixpanel 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 13 Mixpanel SCIM tools

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

- **List all Mixpanel SCIM users** (List). List members of the Mixpanel organization via SCIM (only users whose email domain is a verified claimed domain). Supports a SCIM filter such as userName eq "jane@acme.com". Returns: id, userName, name, emails, active, orgRole, groups.
- **Get single Mixpanel SCIM user by ID** (Get). Get a single Mixpanel organization member by SCIM user id. Returns: id, userName, name, emails, active, orgRole, groups.
- **Create a Mixpanel SCIM user** (Create). Provision a member into the Mixpanel organization via SCIM. userName must be an email on a verified claimed domain; the user is added as an Organization Member (set roles/project access in Mixpanel). Required: schemas, userName, emails.
- **Update a Mixpanel SCIM user by ID** (Update). Replace a Mixpanel member with SCIM PUT (Mixpanel does not support PATCH): update name/email, set active false to deactivate or true to reactivate. Required: id, schemas, userName, emails.
- **Delete a Mixpanel SCIM user by ID** (Delete). Deprovision a Mixpanel member via SCIM DELETE. Depending on organization settings this deactivates or permanently deletes the user and their saved content. Required: id.
- **List all Mixpanel SCIM groups** (List). List Mixpanel Teams exposed as SCIM groups. Supports a SCIM filter such as displayName eq "Analysts". Returns: id, displayName, members.
- **Get single Mixpanel SCIM group by ID** (Get). Get a single Mixpanel Team (SCIM group) by id. Returns: id, displayName, members (SCIM user ids).
- **Create a Mixpanel SCIM group** (Create). Create a Mixpanel Team via SCIM, optionally with members. Roles and project access for the team are set inside Mixpanel. Required: schemas, displayName.
- **Update a Mixpanel SCIM group by ID** (Update). Replace a Mixpanel Team with SCIM PUT (no PATCH support): rename it and/or set its full member list. Required: id, schemas, displayName.
- **Delete a Mixpanel SCIM group by ID** (Delete). Delete a Mixpanel Team (SCIM group); its members remain organization users. Required: id.
- **List all Mixpanel SCIM service provider config** (List). Get Mixpanel's SCIM ServiceProviderConfig: which SCIM features are supported (filter yes; patch, bulk, sort, etag no) and the bearer-token auth scheme. Public endpoint.
- **List all Mixpanel SCIM schemas** (List). List the SCIM schemas Mixpanel implements (User and Group) with their attribute definitions, e.g. orgRole on User. Public endpoint.
- **List all Mixpanel SCIM resource types** (List). List the SCIM resource types Mixpanel exposes (User at /Users, Group at /Groups). Public endpoint.
