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.
- Connects with an API key
- Free 14-day trial
- No credit card
List every Zapier SCIM user who is not in a group
Working in Zapier SCIM with Elaichi
-
List all Zapier SCIM users
-
Get single Zapier SCIM user by ID
-
Zapier SCIM users search
How to connect Zapier SCIM to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Zapier 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.
Zapier 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.
Zapier 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.
Zapier 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.
Zapier 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 Zapier 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 Zapier 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 Zapier SCIM is logged.
-
IT
Provision a new hire's Zapier user
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.
-
HR
Remove a leaver from Zapier
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.
-
Security
Review who is in each Zapier group
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.
-
Finance
Count Zapier seats before renewal
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.
-
Operations
Rename or reshape a Zapier group
Rename a group after a reorg, or replace its membership with the new team list, without editing people one at a time.
-
Compliance
Answer an access review from live records
Search Zapier SCIM users by email or department and hand the auditor a current list, plus the log entry proving when it was pulled.
Try asking
- “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?”
What connecting Zapier SCIM gets you
6 screens from Elaichi, each doing one job for your Zapier SCIM account.
Ask Elaichi to work across your apps.
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?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Zapier SCIM users in plain words.
Type a question and get answers from live Zapier SCIM users and groups.
Copy the endpoint
AI apps
One endpoint brings Zapier SCIM to every client.
Claude, ChatGPT and Cursor reach Zapier SCIM through one governed endpoint, no SDK or shared key.
Tool catalog
17 Zapier SCIM tools, ready without code.
Users, groups, schemas and service provider configs, listed and callable the moment you connect.
Toolboxes
Each team gets its own Zapier SCIM toolbox.
IT provisions users, Security reviews groups, each from a toolbox scoped to that team.
Shared connections
Share one Zapier SCIM connection, keep the key.
One admin connects, teams and members work through it, nobody else sees the API key.
Audit log
Every Zapier SCIM change names who made it.
When, who, what happened, type and resource, for every user or group touched.
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.
Zapier SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Zapier 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
Zapier SCIM
Queued
Workflows
A schedule runs the Zapier SCIM review itself.
New users are fetched, grouped, drafted into a digest, approved, then posted back.
Zapier 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%
HR 27%
Security 21%
Finance 18%
Collections and dashboards
Zapier SCIM seat counts, computed with no model.
Four metrics, 14 days of users created, broken down by team, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Zapier SCIM tools for your AI agents
17 tools are ready to call through Elaichi's MCP endpoint the moment you connect Zapier 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 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 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.
Put Zapier 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