# 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. Source: https://elaichi.ai/connectors/servicenowscim/ ## Facts | | | | --- | --- | | Application | ServiceNow SCIM | | Category | Ticketing | | AI tools | 24 | | Authentication | Connects over OAuth | | Bring 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 | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once ServiceNow SCIM is connected - 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? ## Connect ServiceNow SCIM in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick ServiceNow SCIM. 2. Optionally set Share with, then press Connect. 3. 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. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which ServiceNow SCIM tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## ServiceNow SCIM MCP connector for 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. ## ServiceNow SCIM MCP connector for 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. ## ServiceNow SCIM MCP connector for 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 ServiceNow 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 Every scope the client asks for starts ticked except "Delete data and remove access", which you tick yourself. Calling a ServiceNow SCIM tool needs "Run your connected tools". 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. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with ServiceNow SCIM through Elaichi ### Set up a new hire on day one IT. Create the ServiceNow SCIM user, set their department, cost center and location, and add them to the right groups before their first morning. ### Remove a leaver the same day IT. Pull the person out of every ServiceNow SCIM group and delete their user record as soon as HR confirms the last day. ### Fix departments after a reorganization HR. 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. ### Review who is in each group Security. List every ServiceNow SCIM group and its members ahead of an access review, then remove anyone who should no longer be there. ### Check cost center headcount Finance. List ServiceNow SCIM cost centers and the users assigned to each one, so the chargeback report matches who actually sits where. ### Answer a where-does-this-person-sit question Service desk. Look up a ServiceNow SCIM user by name and see their company, department, location and groups without opening the admin console. ## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## 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 my team share one ServiceNow SCIM connection? Yes. One admin connects ServiceNow SCIM in Elaichi and shares the connection with a team, and nobody else ever handles the client ID or secret. Each teammate still signs in as themselves, so every user or group change in the audit log is tied to the person who made it. ### 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. ## All 24 ServiceNow SCIM tools Every tool below is callable through https://api.elaichi.ai/mcp once ServiceNow SCIM is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all ServiceNow SCIM users** (List). List ServiceNow SCIM user records from the User [sys_user] table. Returns each record's id, userName, displayName, name, emails, active flag, and meta timestamps. Supports attributes/excludedAttributes field selection, RFC7644 filter expressions, and sortBy/sortOrder; page size is capped at 500 records. - **Get single ServiceNow SCIM user by ID** (Get). Get a single ServiceNow SCIM user record from the User [sys_user] table by id (the record's sys_id). Returns the full SCIM user object including id, userName, displayName, name, emails, phoneNumbers, active flag, meta, and ServiceNow extension attributes. Required: id. - **Create a ServiceNow SCIM user** (Create). Create a ServiceNow SCIM user record in the User [sys_user] table. Returns the created user including id, userName, displayName, emails, phoneNumbers, active, and meta timestamps. Does not support search or bulk modifications. - **Delete a ServiceNow SCIM user by ID** (Delete). Delete a ServiceNow SCIM user record from the User [sys_user] table by id. Returns an empty 204 response on success. Required: id. - **ServiceNow SCIM users partial update** (Update). Modify fields of a ServiceNow SCIM user record by id using a SCIM PatchOp body of add, remove, and replace operations. Returns the updated user including id, userName, displayName, active, and meta. Required: id, Operations. - **Update a ServiceNow SCIM user by ID** (Update). Update a ServiceNow SCIM user record in the User [sys_user] table by id. Returns the updated user including id, userName, displayName, emails, active, and the ServiceNow user extension. Required: id. - **Get single ServiceNow SCIM company by ID** (Get). Get a single company record from ServiceNow SCIM by id. Returns: id, meta, name, schemas. Required: id. - **List all ServiceNow SCIM companies** (List). List company records from ServiceNow SCIM. Returns each company's id, name, meta (created, lastModified, location, resourceType), and schemas. No-match queries return an empty result set. - **Get single ServiceNow SCIM cost center by ID** (Get). Get a single ServiceNow SCIM cost center record by id. Returns: schemas, id, name, active, meta. Required: id. - **List all ServiceNow SCIM cost centers** (List). List ServiceNow SCIM cost center records from the Cost Center [cmn_cost_center] table. Returns each cost center with id, name, active, meta (created, lastModified), and schemas. - **Get single ServiceNow SCIM department by ID** (Get). Get a single department record by id from the ServiceNow Department [cmn_department] table via the SCIM protocol. Returns: schemas, id, meta, name. Required: id. - **List all ServiceNow SCIM departments** (List). List department records from the ServiceNow Department [cmn_department] table via the SCIM protocol. Returns each record's schemas, id, meta (created, lastModified, location), and name. A query with no matches returns 200 with no resources. - **Create a ServiceNow SCIM group** (Create). Create a group record in ServiceNow's Group [sys_user_group] table via the SCIM API. Returns the created group including id, displayName, externalId, members, meta (created, lastModified, location), and the ServiceNow extension company. - **Delete a ServiceNow SCIM group by ID** (Delete). Delete a ServiceNow SCIM group record from the Group [sys_user_group] table by id. Returns an empty 204 response on success. Required: id. - **Get single ServiceNow SCIM group by ID** (Get). Get a ServiceNow SCIM group by id. Returns the group record including id, displayName, externalId, members, meta (created, lastModified, location), and the extension company. Required: id. - **List all ServiceNow SCIM groups** (List). List ServiceNow SCIM group records from the Group [sys_user_group] table. Returns group records including id, displayName, externalId, members, and meta (created, lastModified, location); a query with no matches still succeeds with an empty result set. - **ServiceNow SCIM groups patch** (Action). Add, update, or delete fields on a ServiceNow SCIM group record using RFC 7644 PATCH operations. Returns the updated group including id, displayName, externalId, members, meta, and company. Required: group_id. - **Get single ServiceNow SCIM location by ID** (Get). Get a single location record from the Location [cmn_location] table in ServiceNow via the SCIM protocol. Returns: schemas, id, name, meta. Required: id. - **List all ServiceNow SCIM locations** (List). List location records from the Location [cmn_location] table in ServiceNow via the SCIM protocol. Returns: schemas, id, name, meta. Queries with no matches return 200 with totalResults set to 0. - **Get single ServiceNow SCIM resource type by ID** (Get). Get a single SCIM resource type in servicenowscim by name — one of User, Group, Company, Department, CostCenter, or Location. Returns: schemas, id, name, description, endpoint, schema, schemaExtensions, meta. Required: resource_name. - **List all ServiceNow SCIM resource types** (List). List all SCIM resource types supported by the servicenowscim instance. Returns for each: id, name, description, endpoint, schema, schemaExtensions, and meta. - **Get single ServiceNow SCIM schema by ID** (Get). Get a single SCIM schema definition from the ServiceNow instance by its URN id, e.g. urn:ietf:params:scim:schemas:custom:servicenow:2.0:Department. Returns: id, name, description, attributes, meta, schemas. Required: id (schema URN). - **List all ServiceNow SCIM schemas** (List). List all SCIM resource schemas supported by the ServiceNow instance, defining the attributes available for each resource type (User, Group, Company, CostCenter, Department, Location). Returns each schema's id, name, description, attributes, and meta. - **Get single ServiceNow SCIM service provider config by ID** (Get). Get the ServiceNow SCIM service provider configuration for the instance. Returns the capabilities of the instance's SCIM endpoints: schemas, patch, bulk, filter, changePassword, sort, etag, and authenticationSchemes.