HRIS
Twilio SCIM MCP connector
The Twilio SCIM connector lets Claude, ChatGPT, Cursor, 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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Twilio SCIM to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Twilio SCIM once
-
Open Connections, choose Add connection, and pick Twilio SCIM.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Twilio SCIM app, then approve. Twilio SCIM needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Twilio SCIM to 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.
Connect Twilio SCIM to 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 today. The plugin directory lives at chatgpt.com/plugins.
Connect Twilio SCIM to 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.
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.
Use cases
What teams do with Twilio SCIM through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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?”
AI tools
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.
See it in Elaichi
What connecting Twilio SCIM gets you
6 screens from the product, each doing one job for your Twilio SCIM account.
The agent
Ask about Twilio SCIM users in plain language.
Three starter prompts read live Twilio SCIM users and answer without a console.
- users
- user records
- email addresses
- display names
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Every client reaches Twilio SCIM users over OAuth, with no SDK or shared API key.
Copy the endpoint
Tool catalog
6 Twilio SCIM tools, zero custom code.
Create, read, list, update, patch and delete Twilio SCIM users from one catalog.
- Create a Twilio SCIM user
- Get single Twilio SCIM user by ID
- List all Twilio SCIM users
- Update a Twilio SCIM user by ID
Toolboxes
Every team gets its own Twilio SCIM toolbox.
Toolboxes scope IT, HR and support to the Twilio SCIM user tools they need.
- IT operations
- People operations
- Security
- Support
Shared connections
Teammates provision users without seeing a credential.
The connections table shows who connected each Twilio SCIM account and its shared teams.
- IT core
- People ops
- Security
- Support desk
Audit log
Every Twilio SCIM user change has a name on it.
When, who, what happened, type and resource for each Twilio SCIM call.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
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 digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
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 Michael Brennan
Approve Deny -
Post the digest
Twilio SCIM
Queued
Collections and dashboards
Twilio SCIM user counts arrive already computed.
Four metrics, 14 days of users created and a team breakdown, refreshed on schedule.
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 blocking deletions for a whole team, 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 blocking updates or deletions. A blocked action is never shown to Claude, ChatGPT, or any other client, so no prompt, however worded, can reach it.
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, and every other client at the same time.
Put Twilio SCIM in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.