# 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. Source: https://elaichi.ai/connectors/twilioscim/ ## Facts | | | | --- | --- | | Application | Twilio SCIM | | Category | HRIS | | AI tools | 6 | | Authentication | Connects over OAuth | | Needs your own OAuth app | Yes | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Twilio SCIM is connected - 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? ## Connect Twilio SCIM in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Twilio SCIM. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Twilio SCIM tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Twilio SCIM to 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. ## Connect Twilio SCIM to 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 today. The plugin directory lives at chatgpt.com/plugins. ## Connect Twilio SCIM to 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. ## Connect Twilio 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 Only Read is granted by default, which is not enough to call a Twilio SCIM tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Twilio SCIM through Elaichi ### Set up a new hire's Twilio account IT. Create the Twilio user for someone starting Monday from the details in the hiring ticket, without opening the admin console. ### Remove access the day someone leaves HR. Ask for a departing employee's Twilio user to be deleted as part of the offboarding checklist, and see it confirmed in the log. ### Run an access review of Twilio users Security. List every Twilio user, spot accounts that belong to people who have moved teams or left, and flag them for cleanup. ### Fix a name or email after a change People Ops. Update a Twilio user's display name, email, or department after a legal name change or a team move, in one request. ### Check a single user's account details IT helpdesk. Pull up one Twilio user by ID to confirm whether an account exists and what it currently says before answering a ticket. ### Correct one field without touching the rest Compliance. Make a partial update to a Twilio user, such as marking the account inactive, and leave every other attribute exactly as it was. ## 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 my team share one Twilio SCIM connection? Yes. One administrator connects Twilio SCIM in Elaichi and shares the connection with a team, so nobody else ever sees the client ID or secret. Each teammate still signs in to Elaichi as themselves, so every Twilio user created, updated, or removed is recorded against their name. ### 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. ## All 6 Twilio SCIM tools Every tool below is callable through https://api.elaichi.ai/mcp once Twilio SCIM is connected, subject to the toolbox it is in and the restrictions on the caller. - **Create a Twilio SCIM user** (Create). Create a Twilio SCIM user using the core user schema. Returns: id, externalId, userName, displayName, name, emails, active, locale, timezone, schemas, meta. Required: userName, emails. The userName must match the primary email address and the user's email domain must be verified by the organization. - **Get single Twilio SCIM user by ID** (Get). Get a single Twilio SCIM user by their user SID. Returns: id, externalId, userName, displayName, name, emails, active, locale, timezone, schemas, meta. Required: id. - **List all Twilio SCIM users** (List). List Twilio SCIM users, optionally filtered by userName or externalId. Returns: id, externalId, userName, displayName, name, emails, active, locale, timezone, schemas, meta. Only the eq filter operator is supported; SCIM pagination parameters (startIndex, itemsPerPage) are not supported. - **Update a Twilio SCIM user by ID** (Update). Update a Twilio SCIM user by id, replacing all user attributes. Returns: id, externalId, userName, displayName, name, emails, active, locale, timezone, schemas, meta. Required: id. Only active and inactive users can be updated; the Organization Owner can't be updated through this endpoint. - **Delete a Twilio SCIM user by ID** (Delete). Deactivate a Twilio SCIM user by id. Users aren't permanently deleted; they're deactivated in response to delete requests. Returns an empty 204 response on success. Required: id. The Organization Owner can't be deactivated through this endpoint. - **Twilio SCIM users partial update** (Update). Partially update a Twilio SCIM user by id using SCIM PatchOp operations. Returns the updated user object including id, userName, displayName, emails, active, and meta. Required: id. Only active and inactive users can be patched; suspended users can't be patched. The Organization Owner can't be patched through this endpoint. If any operation violates business rules, the entire request is rejected.