Skip to content

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.

1

In Elaichi

Connect Twilio SCIM once

  1. Open Connections, choose Add connection, and pick Twilio SCIM.

  2. Optionally set Share with to give a team access, 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.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

twilio scim
Twilio SCIM
360learning
7shifts
BambooHR
Charlie
Deel
2

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. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 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. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 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. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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?”

See all 6 Twilio SCIM tools below

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.

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.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

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
ElaichiTools
Tool Action Description
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.

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
ElaichiToolboxes
Name Source template Tools Created

IT operations toolbox

Twilio SCIM · user provisioning and deprovisioning

Twilio SCIM starter 18 Mar 4, 2026

People operations toolbox

Twilio SCIM · joiners, movers and leavers

9 Mar 2, 2026

Security toolbox

Twilio SCIM · user access reviews

24 Feb 27, 2026

Support toolbox

Twilio SCIM · user lookups and resets

Twilio SCIM starter 6 Feb 19, 2026

Engineering toolbox

Twilio SCIM · user record fixes

31 Jan 30, 2026

Compliance toolbox

Twilio SCIM · user change evidence

12 Jan 22, 2026

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
ElaichiConnections
Connection Scope Status Access
TW

Twilio SCIM (IT core)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
TW

Twilio SCIM (People ops)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
TW

Twilio SCIM (Security)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
TW

Twilio SCIM (Support desk)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
TW

Twilio SCIM (Contractors)

Connected by Clara Nowak

Personal • Active Not shared
TW

Twilio SCIM (EMEA)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

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
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Twilio SCIM Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Twilio SCIM Users Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Twilio SCIM Users List Toolbox

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

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch users

    Twilio SCIM

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. 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

Live

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%

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

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.