Skip to content

Ticketing

ServiceNow MCP connector

The ServiceNow connector brings incidents, user accounts, roles, and tables into Claude, ChatGPT, Cursor, and other AI clients, so people can raise, update, and review ServiceNow records inside their own access while every action is logged.

  • How it connects. App credentials. 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 ServiceNow to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect ServiceNow once

  1. Open Connections, choose Add connection, and pick ServiceNow.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste your ServiceNow app credentials. ServiceNow authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

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

Add connection

Choose a connector.

servicenow
ServiceNow
Airtable
Asana
Autotask
Basecamp
ClickUp
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 ServiceNow 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 ServiceNow 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 ServiceNow 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 ServiceNow 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 ServiceNow through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • IT service desk

    Raise an incident from a chat message

    Describe the outage in plain language and have a ServiceNow incident created with the right short description, urgency, and assignment group. The record is ready before the caller hangs up.

  • IT service desk

    Catch an incident up after a call

    Update the incident with what the user said, change its state, and reassign it without opening ServiceNow. The full record stays where the rest of the team expects it.

  • IT operations

    Summarize open incidents before standup

    Ask for every open incident assigned to your group, grouped by priority, and get a plain summary of what is stuck and who owns it.

  • People operations

    Set up a new hire's ServiceNow account

    Create the user record with name, email, department, and manager on day one, then grant the roles their job needs. Corrections later are a one line ask.

  • Security and compliance

    Check who holds an admin role

    List the roles assigned to any ServiceNow user and confirm that access matches their current job. Remove a role the moment someone changes teams.

  • Platform administration

    Review custom tables without a console

    List the tables defined in your ServiceNow instance, look up any one by name, and check its label and settings before a change window.

Try asking

  • “Which sys_users gained new roles this week?”
  • “Summarize open incidents assigned to the service desk.”
  • “List sys_user_roles with more than twenty members.”

See all 96 ServiceNow tools below

AI tools

ServiceNow tools for your AI agents

96 tools are ready to call through Elaichi's MCP endpoint the moment you connect ServiceNow, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting ServiceNow gets you

6 screens from the product, each doing one job for your ServiceNow account.

The agent

Ask in plain language, read live ServiceNow records.

Questions about users, roles and tables answered from live ServiceNow records.

  • incidents
  • users
  • roles
  • tables

Ask Elaichi to work across your apps.

Which sys_users gained new roles this week?

Summarize open incidents assigned to the service desk.

List sys_user_roles with more than twenty members.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Connect any MCP client to ServiceNow over OAuth, no SDK, no 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

96 ServiceNow tools ready without custom code.

Browse tool names, resources and methods across users, roles and tables.

  • List all ServiceNow sys users
  • Get single ServiceNow sys user by ID
  • Create a ServiceNow sys user
  • Update a ServiceNow sys user by ID
ElaichiTools
Tool Action Description
List all ServiceNow sys users List List sys_users records in ServiceNow. Returns fields such as sys_id, sys_created_on, sys_updated_on, active, and name for each user. Requires specifying the sys_users table.
Get single ServiceNow sys user by ID Get Get details about a specific sys_user in ServiceNow by id. Returns key fields such as sys_id, name, email, active status, roles, creation and update timestamps, and reference links.
Create a ServiceNow sys user Create Create a sys_users record in ServiceNow. Returns fields of the new user record such as sys_id, user_name, name, and email. Only single record insertion is supported.
Update a ServiceNow sys user by ID Update Update sys_users record in ServiceNow using id. Returns updated fields such as sys_id, user_name, and other key attributes in the response.
Delete a ServiceNow sys user by ID Delete Delete a specific sys_users record in ServiceNow. Requires id. No content is returned in the response.

Toolboxes

Every team gets its own ServiceNow toolbox.

Service desk, IT operations and compliance each work from a separate curated toolbox.

  • Service desk
  • IT operations
  • Identity and access
  • Change management
ElaichiToolboxes
Name Source template Tools Created

Service desk toolbox

ServiceNow · incidents and requests

ServiceNow starter 18 Mar 4, 2026

IT operations toolbox

ServiceNow · tables and records

9 Mar 2, 2026

Identity and access toolbox

ServiceNow · sys_users and roles

24 Feb 27, 2026

Change management toolbox

ServiceNow · change records and approvals

ServiceNow starter 6 Feb 19, 2026

Compliance toolbox

ServiceNow · role audits and access reviews

31 Jan 30, 2026

Platform engineering toolbox

ServiceNow · sys_db_object schemas

12 Jan 22, 2026

Shared connections

Teammates use ServiceNow accounts, never the credential.

See who connected each account and how many teams and members share it.

  • Service desk
  • IT operations EMEA
  • Identity and access
  • Change management
ElaichiConnections
Connection Scope Status Access
SE

ServiceNow (Service desk)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
SE

ServiceNow (IT operations EMEA)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
SE

ServiceNow (Identity and access)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
SE

ServiceNow (Change management)

Connected by Daniel Ortega

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

ServiceNow (Compliance)

Connected by Clara Nowak

Personal • Active Not shared
SE

ServiceNow (Platform engineering)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Answer who changed which ServiceNow record.

Every call logged with time, actor, action, type and ServiceNow resource.

  • 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]

ServiceNow Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

ServiceNow Incidents Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

ServiceNow Incidents 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 starts work, a person approves it.

Fetch ServiceNow incidents, group them, draft a digest, approve, then post back.

ServiceNow digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch incidents

    ServiceNow

    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

    ServiceNow

    Queued

Collections and dashboards

ServiceNow health numbers land before anyone asks.

Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.

ServiceNow health

Refreshed 4 minutes ago · every 15 minutes · from the incidents collection

Live

Incidents

1,284 ↓ 12%

Users

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Incidents created

Last 14 days

By team

Share of activity

Service desk 34%

IT operations EMEA 27%

Identity and access 21%

Change management 18%

FAQ

Frequently asked questions

How do I connect ServiceNow to Claude?

Connect ServiceNow in Elaichi by entering your ServiceNow instance app credentials when prompted. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in to Elaichi when Claude asks and your ServiceNow incidents, users, roles, and tables are available in the conversation.

Does ServiceNow work with ChatGPT and Cursor as well as Claude?

Yes. Once ServiceNow 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 ServiceNow once and every client you sign in to sees it, with the same access and the same audit log.

What can an AI agent actually do with my ServiceNow data?

An agent can look up and list ServiceNow incidents, create a new one, update fields like state, assignment group, and work notes, and close or delete a record where you are allowed to. It can also list ServiceNow users and their roles, create or update a user account, grant or remove a role, and look up the tables defined in your instance. Because ServiceNow has many actions available, short concrete asks like "reassign INC0012345 to the network team" work better than long paragraphs.

Does connecting ServiceNow give the AI access to my whole instance?

No. Every call to ServiceNow runs as the person who signed in, so the agent sees only the incidents, users, roles, and tables that person's own ServiceNow roles and access controls already allow. Elaichi can narrow that further by hiding actions for a team, but it can never widen access beyond what ServiceNow itself grants that person.

Can my team share one ServiceNow connection?

Yes. One administrator connects ServiceNow in Elaichi and shares the connection with a team, and nobody else ever handles the ServiceNow credential. Each teammate still signs in to Elaichi as themselves, so every incident update or role change in the audit log is attributed to the person who made it, not to a shared account.

Can I stop an agent from deleting or changing things in ServiceNow?

Yes. Restrictions in Elaichi apply per action, so you can allow reading and creating ServiceNow incidents while blocking updates, deletes, or any change to users and roles. A blocked action is never advertised to Claude, ChatGPT, or Cursor at all, so no prompt, however worded, can reach it.

What happens to a ServiceNow connection when someone leaves?

Offboarding the person in Elaichi ends their access to ServiceNow through every AI client at once, with no need to touch each client separately. A shared ServiceNow connection keeps working for everyone else on the team. If you ever want to remove ServiceNow entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client.

Put ServiceNow in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.