# Zapier SCIM MCP connector

The Zapier SCIM connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent list, create, update and remove Zapier users and groups, inside each person's own access, with every call logged.

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

## Facts

| | |
| --- | --- |
| Application | Zapier SCIM |
| Category | Application Development |
| AI tools | 17 |
| 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 Zapier SCIM is connected

- List every Zapier SCIM user who is not in a group
- Add Priya Shah to the Finance group in Zapier
- Which Zapier SCIM users were created this month?

## Connect Zapier SCIM in Elaichi

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

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

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

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

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

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

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

### Provision a new hire's Zapier user

IT. Ask for a Zapier user to be created from the new hire's name and email, then dropped into the right group. The ticket closes without anyone opening the Zapier admin console.

### Remove a leaver from Zapier

HR. On someone's last day, ask for their Zapier SCIM user to be deactivated or deleted and pulled out of every group. The audit log shows who did it and when.

### Review who is in each Zapier group

Security. Pull the members of every Zapier group into one view and spot people who should no longer be there. Fix the stragglers in the same conversation.

### Count Zapier seats before renewal

Finance. List all Zapier SCIM users and see how many are active, how many belong to each group, and which ones look unused before the next invoice.

### Rename or reshape a Zapier group

Operations. Rename a group after a reorg, or replace its membership with the new team list, without editing people one at a time.

### Answer an access review from live records

Compliance. Search Zapier SCIM users by email or department and hand the auditor a current list, plus the log entry proving when it was pulled.

## Elaichi vs Zapier MCP vs Composio for Zapier SCIM

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

Two steps. First, connect Zapier SCIM in Elaichi by pasting in your Zapier SCIM API key, which is the only sign-in it needs, 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. Claude signs you into Elaichi and Zapier SCIM is available right away.

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

Yes. Once Zapier 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. You connect Zapier SCIM once and every client picks it up.

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

It can list and search your Zapier users and groups, look up one person by ID or email, create a user, update or replace their details, move them into or out of a group, and delete them when they leave. It can also read your Zapier SCIM schema and service provider settings when you need to check what fields are supported. Short, concrete asks such as "add Priya to the Finance group" work better than long paragraphs.

### Does connecting Zapier SCIM give the AI every user and group in my Zapier account?

Access follows the person who signed in and the Zapier SCIM API key behind the connection, so the agent can only see and change what that combination already allows. Elaichi can narrow that further with roles and restrictions, for example read-only for most people, but it can never widen what Zapier SCIM itself permits.

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

Yes. One admin connects Zapier SCIM in Elaichi and shares it with a team, and nobody else ever handles or sees the API key. Each teammate still signs in to Elaichi as themselves, so every Zapier user or group change in the audit log carries their name, not the admin's.

### Can I stop an agent from deleting or changing things in Zapier SCIM?

Yes. Restrictions in Elaichi work per action, so you can allow listing and searching Zapier SCIM users while restricting create, update, replace and delete, on a role or on one person. A restricted tool still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a Zapier SCIM connection when someone leaves?

Offboarding that person in Elaichi ends their access to Zapier SCIM at once, across Claude, ChatGPT, Cursor, Microsoft Copilot and every other client. A shared Zapier SCIM connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Zapier SCIM once in Elaichi removes it from every client.

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

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

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

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

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

- **List all Zapier SCIM users** (List). List members of the Zapier Enterprise account via SCIM, 50 per page. Supports SCIM filter (e.g. userName eq "jane@acme.com"), sortBy/sortOrder and attributes. Deactivated users are hidden. Returns: id, userName, name, emails, active.
- **Get single Zapier SCIM user by ID** (Get). Get a single Zapier member by SCIM user id. Returns: id, userName, displayName, name, emails, active, timezone, groups.
- **Create a Zapier SCIM user** (Create). Create (provision) a member in the Zapier Enterprise account. userName must be an email on a verified domain; returns 409 if a user with that email exists. Required: schemas, userName.
- **Update a Zapier SCIM user by ID** (Update). Partially update a Zapier member with SCIM PATCH (PatchOp). Only add and replace ops are supported, e.g. {"op":"replace","value":{"active":false}} to deactivate or active true to reactivate. Required: id, schemas, Operations.
- **Delete a Zapier SCIM user by ID** (Delete). Deprovision a Zapier member. The user is deactivated, not deleted: their team memberships are revoked, shared Zaps/connections move to the owner and unshared Zaps pause. The account owner cannot be deprovisioned. Required: id.
- **Zapier SCIM users replace** (Action). Replace a Zapier member with SCIM PUT, overwriting every attribute (omitted ones are cleared). Send active true to reactivate a suspended member. Required: user_id, schemas, userName.
- **Zapier SCIM users search** (Search). Search Zapier members by posting a SCIM filter in the body (POST /Users/.search), same semantics as the list filter. Required: filter. Returns: Resources with id, userName, name, emails, active.
- **List all Zapier SCIM groups** (List). List teams (SCIM groups) in the Zapier Enterprise account, 50 per page. Supports SCIM filter (e.g. displayName eq "Engineering"), sortBy/sortOrder and attributes. Returns: id, displayName, members.
- **Get single Zapier SCIM group by ID** (Get). Get a single Zapier team by SCIM group id. Returns: id, displayName, members (value = user id, display).
- **Create a Zapier SCIM group** (Create). Create a team in the Zapier Enterprise account, optionally with members. displayName must be unique (409 if a team with that name exists). Required: schemas, displayName.
- **Update a Zapier SCIM group by ID** (Update). Partially update a Zapier team with SCIM PATCH: rename it (replace displayName), add members (op add, path members), replace all members, or remove members (op remove, path members[value eq "&lt;id&gt;"]). Required: id, schemas, Operations.
- **Zapier SCIM groups replace** (Action). Replace a Zapier team with SCIM PUT, overwriting its name and full member list. Required: group_id, schemas, displayName.
- **Delete a Zapier SCIM group by ID** (Delete). Delete a Zapier team and remove all of its memberships; the users themselves stay active. Required: id.
- **Zapier SCIM groups search** (Search). Search Zapier teams by posting a SCIM filter in the body (POST /Groups/.search). Required: filter. Returns: Resources with id, displayName, members.
- **List all Zapier SCIM me** (List). Get the Zapier account owner (the user the SCIM token belongs to). Zapier redirects to that user's /Users/{id} record. Returns: id, userName, name, emails, active.
- **List all Zapier SCIM service provider configs** (List). Get Zapier's SCIM service provider configuration: which features (patch, bulk, filter, sort, etag, changePassword) and authentication schemes are supported.
- **Get single Zapier SCIM schema by ID** (Get). Get the SCIM schema Zapier uses for a resource type. Use id Users or Groups. Returns: id, name, attributes (name, type, required, mutability).
