Twilio SCIM MCP connector
The Twilio SCIM connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, and Elaichi's own agent create, look up, update, and remove Twilio user accounts through one governed endpoint, with each person signed in as themselves and every change recorded in an audit log.
- Connects over OAuth
- Free 14-day trial
- No credit card
List all Twilio SCIM users created this month.
Working in Twilio SCIM with Elaichi
-
Get single Twilio SCIM user by ID
-
List all Twilio SCIM users
-
Create a Twilio SCIM user
How to connect Twilio SCIM to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Twilio 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.
Twilio 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.
Twilio 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.
Twilio 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.
Twilio 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 Twilio 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 Twilio 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 Twilio SCIM is logged.
-
IT
Set up a new hire's Twilio account
Create the Twilio user for someone starting Monday from the details in the hiring ticket, without opening the admin console.
-
HR
Remove access the day someone leaves
Ask for a departing employee's Twilio user to be deleted as part of the offboarding checklist, and see it confirmed in the log.
-
Security
Run an access review of Twilio users
List every Twilio user, spot accounts that belong to people who have moved teams or left, and flag them for cleanup.
-
People Ops
Fix a name or email after a change
Update a Twilio user's display name, email, or department after a legal name change or a team move, in one request.
-
IT helpdesk
Check a single user's account details
Pull up one Twilio user by ID to confirm whether an account exists and what it currently says before answering a ticket.
-
Compliance
Correct one field without touching the rest
Make a partial update to a Twilio user, such as marking the account inactive, and leave every other attribute exactly as it was.
Try asking
- “List all Twilio SCIM users created this month.”
- “Deactivate the Twilio SCIM user for Priya Raman.”
- “Which Twilio SCIM users are missing an email address?”
What connecting Twilio SCIM gets you
6 screens from Elaichi, each doing one job for your Twilio SCIM account.
Ask Elaichi to work across your apps.
List all Twilio SCIM users created this month.
Deactivate the Twilio SCIM user for Priya Raman.
Which Twilio SCIM users are missing an email address?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Twilio SCIM users in plain language.
Three starter prompts read live Twilio SCIM users and answer without a console.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.
Every client reaches Twilio SCIM users over OAuth, with no SDK or shared API key.
Tool catalog
6 Twilio SCIM tools, zero custom code.
Create, read, list, update, patch and delete Twilio SCIM users from one catalog.
Toolboxes
Every team gets its own Twilio SCIM toolbox.
Toolboxes scope IT, HR and support to the Twilio SCIM user tools they need.
Shared connections
Teammates provision users without seeing a credential.
The connections table shows who connected each Twilio SCIM account and its shared teams.
Audit log
Every Twilio SCIM user change has a name on it.
When, who, what happened, type and resource for each Twilio 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. Automations, collections and live dashboards come with the Black plan.
Twilio SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
Twilio 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
Twilio SCIM
Queued
Automations
A schedule provisions Twilio SCIM users end to end.
Six steps fetch users, group them, draft a digest, take approval, then write back.
Twilio SCIM health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
User records
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
IT core 34%
People ops 27%
Security 21%
Support desk 18%
Collections and dashboards
Twilio SCIM user counts arrive already computed.
Four metrics, 14 days of users created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Twilio SCIM
All three can connect Twilio 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 Twilio SCIM tools | Allow or restrict single Twilio 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 Twilio 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.
Twilio SCIM tools for your AI agents
6 tools are ready to call through Elaichi's MCP endpoint the moment you connect Twilio 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 Twilio SCIM to Claude?
Connect Twilio SCIM in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Twilio SCIM signs in over OAuth, but it needs an OAuth application registered inside Twilio SCIM itself, so an administrator brings a client ID and secret once when setting up the connection. After that, everyone else simply signs in as themselves and never handles those details.
Does Twilio SCIM work with ChatGPT and Cursor as well as Claude?
Yes. Once Twilio 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 Twilio SCIM once and use it from whichever client you happen to be in.
What can an AI agent actually do with my Twilio SCIM data?
An agent can create a Twilio user account for a new hire, look up a single user by ID, list all Twilio users, update a user's name, email, or department, make a small change to one field, and delete a user who has left. That covers the everyday provisioning work an IT or HR team does in Twilio SCIM, asked for in plain language.
Does connecting Twilio SCIM give the AI full admin rights over every user?
No. Access through Twilio SCIM follows the person who signed in, so the AI can only do what that person's own Twilio account already allows. Elaichi can narrow that further, for example by restricting deletions for everyone in a role, but it can never grant more than the person already has.
Can I stop an agent from deleting or changing users in Twilio SCIM?
Yes. In Elaichi you restrict Twilio SCIM actions one by one, so you can allow looking up and listing users while restricting updates or deletions. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
What happens to a Twilio SCIM connection when someone leaves?
Offboarding that person in Elaichi ends their access to Twilio SCIM at once, across every client they used. If they shared a Twilio SCIM connection with a team, it keeps working for everyone else. If you want it gone entirely, disconnecting Twilio SCIM once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.
Does the Twilio SCIM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Twilio 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 Twilio SCIM?
Yes. Both let Claude, ChatGPT or Cursor use Twilio 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 Twilio SCIM call.
How is Elaichi different from Composio for Twilio 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 Twilio 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 Twilio 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