ServiceNow SCIM MCP connector
The ServiceNow SCIM connector brings users, groups, departments, cost centers and locations into Claude, ChatGPT, Cursor and the Elaichi Agent, so each person can look up and manage ServiceNow SCIM accounts within their own access.
-
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.
24 tools
How to connect
How to connect ServiceNow SCIM to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect ServiceNow SCIM once
-
Open Connections, choose Add connection, and pick ServiceNow SCIM.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own ServiceNow SCIM app, then approve. ServiceNow 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.
ServiceNow 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.
ServiceNow 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 today. The plugin directory lives at chatgpt.com/plugins.
ServiceNow 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.
Connect ServiceNow 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 ServiceNow 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 on day one
Create the ServiceNow SCIM user, set their department, cost center and location, and add them to the right groups before their first morning.
-
IT
Remove a leaver the same day
Pull the person out of every ServiceNow SCIM group and delete their user record as soon as HR confirms the last day.
-
HR
Fix departments after a reorganization
When a team moves, update each affected ServiceNow SCIM user with the new department and cost center instead of editing records one at a time.
-
Security
Review who is in each group
List every ServiceNow SCIM group and its members ahead of an access review, then remove anyone who should no longer be there.
-
Finance
Check cost center headcount
List ServiceNow SCIM cost centers and the users assigned to each one, so the chargeback report matches who actually sits where.
-
Service desk
Answer a where-does-this-person-sit question
Look up a ServiceNow SCIM user by name and see their company, department, location and groups without opening the admin console.
Try asking
- “List every user in the Finance department with their cost center.”
- “Add Priya Shah to the Service Desk group.”
- “Which users are assigned to the London location?”
Compare
Elaichi vs Zapier MCP vs Composio for ServiceNow SCIM
All three can connect ServiceNow 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 ServiceNow SCIM tools | Allow or restrict single ServiceNow 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 ServiceNow 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 | $15 per user per month. | 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.
AI tools
ServiceNow SCIM tools for your AI agents
24 tools are ready to call through Elaichi's MCP endpoint the moment you connect ServiceNow 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 ServiceNow SCIM gets you
6 screens from the product, each doing one job for your ServiceNow SCIM account.
The agent
Ask about users and groups in plain words.
Three starter prompts answer from live ServiceNow SCIM users, groups and departments.
- users
- groups
- departments
- cost centers
Ask Elaichi to work across your apps.
List every user in the Finance department with their cost center.
Add Priya Shah to the Service Desk group.
Which users are assigned to the London location?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint, every client, no shared API key.
Claude, ChatGPT and Cursor reach ServiceNow SCIM through one governed org endpoint over OAuth.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
24 ServiceNow SCIM tools, no code to write.
Users, groups, departments, cost centers, locations and schemas, each listed with its resource and method.
- List all ServiceNow SCIM users
- Get single ServiceNow SCIM user by ID
- Create a ServiceNow SCIM user
- Delete a ServiceNow SCIM user by ID
ElaichiToolsToolboxes
Every team gets its own ServiceNow SCIM toolbox.
IT provisions users, HR reads departments, Security reviews groups, each from a toolbox scoped to them.
- IT
- HR
- Security
- Finance
ElaichiToolboxesShared connections
Teammates work through a connection, never a credential.
One admin connects ServiceNow SCIM once, shares it with teams, and nobody else sees a secret.
- IT Admin
- HR Ops
- Security
- Finance
ElaichiConnectionsAudit log
Every ServiceNow SCIM change names who did it.
When, who, what happened, type and resource, written to an append-only log for every call.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching 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 starts work, a person approves it.
ServiceNow SCIM users are fetched, grouped by department, drafted into a digest, approved, then posted back.
ServiceNow SCIM digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
ServiceNow 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
ServiceNow SCIM
Queued
Collections and dashboards
ServiceNow SCIM numbers, computed, with no model involved.
Four metrics, a 14 day chart of users created, a breakdown by team, refreshed on schedule.
ServiceNow 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 Admin 34%
HR Ops 27%
Security 21%
Finance 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect ServiceNow SCIM to Claude?
Connect ServiceNow SCIM in Elaichi first, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. ServiceNow SCIM signs you in over OAuth, but it needs an OAuth application registered inside ServiceNow SCIM itself, so one admin brings a client ID and secret once when the connection is created. After that, everyone else signs in with their own ServiceNow SCIM login and never touches that secret.
Does ServiceNow SCIM work with ChatGPT and Cursor as well as Claude?
Yes. The same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. Connect ServiceNow SCIM once in Elaichi and every client picks it up without a second setup.
What can an AI agent actually do with my ServiceNow SCIM data?
It can list and look up ServiceNow SCIM users, groups, companies, departments, cost centers and locations, and it can create, update or delete users and groups when you ask. Ask it to find everyone in a department, add someone to a group, or change a user's cost center after a transfer. Short, concrete asks like add Priya to the Service Desk group work better than long paragraphs.
Does connecting ServiceNow SCIM give the AI everything in my instance?
No. The AI acts inside the ServiceNow SCIM access of the person who signed in, so it can only see the users, groups and departments that person could already see. Elaichi can narrow that further with toolboxes and restrictions, and it can never widen it beyond what ServiceNow SCIM itself allows.
Can I stop an agent from deleting or changing users in ServiceNow SCIM?
Yes. Restrictions in Elaichi apply per action, so you can allow looking up ServiceNow SCIM users and groups while blocking create, update and delete. A restricted action is left out of the AI client's tool list entirely, so it cannot be called no matter what the prompt says.
What happens to a ServiceNow SCIM connection when someone leaves?
Offboarding that person in Elaichi ends their access to ServiceNow SCIM through every AI client at once. A connection shared with the team keeps working for everyone else. If you want it gone completely, disconnect ServiceNow SCIM once in Elaichi and it disappears from Claude, ChatGPT, Cursor and the Elaichi Agent together.
Does the ServiceNow SCIM MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. ServiceNow 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, 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 ServiceNow SCIM?
Yes. Both let Claude, ChatGPT or Cursor use ServiceNow 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 ServiceNow SCIM call.
How is Elaichi different from Composio for ServiceNow 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 ServiceNow 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 ServiceNow SCIM in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.