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.
In Elaichi
Connect ServiceNow once
-
Open Connections, choose Add connection, and pick ServiceNow.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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
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.
Connect ServiceNow to 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.
Connect ServiceNow to 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 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 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.”
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.
No tools match your search.
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.
Copy the endpoint
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
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
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
Audit log
Answer who changed which ServiceNow record.
Every call logged with time, actor, action, type and ServiceNow resource.
- When
- Who
- What happened
- Type
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
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch incidents
ServiceNow
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
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
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%
Related connectors
More from the catalog
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 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.