ServiceNow MCP Server

io.github.jschullerPublished by GitHub account jschullerv0.9.3Updated Oct 30, 2026

ServiceNow MCP server: Table API, CMDB, schema, aggregates, update sets and four Agent Skills.

VerifiedSTDIODesktop onlyDatabases Productivity & Workflow Business & Commerce

Server details

Identifier: io.github.jschuller/mcp-server-servicenow
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account jschuller for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.jschuller%2Fmcp-server-servicenow.svg)](https://sourceweft.com/mcp/io.github.jschuller%2Fmcp-server-servicenow?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Connects an assistant to a ServiceNow instance so it can query tables, read schemas and CMDB data, run aggregates and review update sets.

What you can do: Query, create, update and delete records in any ServiceNow table, and run aggregate counts and stats
List, read and write CMDB configuration items and follow their relationships
Inspect table schemas, the current user, system properties and where a table or field is referenced
List, read and create update sets, set the current one and review its changes
Read packaged resources such as schemas, instance info and the CMDB class hierarchy, plus four guided skill workflows
When to use it: Useful when you work with ServiceNow ITSM or CMDB data and want an assistant to answer questions about records, fields, roles, data quality or pending update sets without clicking through the platform. It suits developers and admins on a developer instance or a company instance with an integration user.
Requirements: Runs locally as a Python package started with uvx, so uv must be installed. Needs SERVICENOW_INSTANCE_URL plus credentials: SERVICENOW_USERNAME and SERVICENOW_PASSWORD for basic auth, or SERVICENOW_CLIENT_ID and SERVICENOW_CLIENT_SECRET for OAuth, or SERVICENOW_API_KEY. Network access to the instance is required, and the user's ServiceNow roles decide what is visible.

Before you install

It holds ServiceNow credentials (SERVICENOW_PASSWORD, SERVICENOW_CLIENT_SECRET, SERVICENOW_API_KEY) in the client configuration, so keep them out of shared files. Write tools create, update and delete records, CIs and update sets; use SERVICENOW_READ_ONLY or a read-only identity where clients do not confirm writes. SERVICENOW_ALLOW_JS_QUERIES permits arbitrary javascript in queries. Update sets and system properties need admin roles. Data goes only to your instance.

Installation

In SourceWeft

Open ServiceNow MCP Server in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[ServiceNow MCP Server]

ServiceNow MCP Server

[PyPI] [Downloads] [CI] [License]

Connect Claude Code, GitHub Copilot, Codex, opencode, Antigravity or any MCP client to ServiceNow:
query any table, read schema and CMDB, review update sets. Free, MIT, works on a free developer instance.

uvx mcp-server-servicenow gives an AI assistant the ServiceNow developer data plane: the Table API, the data dictionary, Stats API aggregates, the CMDB and update sets, on any release from Tokyo up. It runs alongside ServiceNow's own MCP servers (how they differ).

What you can ask

"Which fields does cmdb_ci_server have, including inherited ones?"
"Who holds admin, and which roles are granted directly instead of through a group?"
"Review update set 'Q3 fixes' before I promote it."
"Which server CIs are missing an IP address or an owner?"
"How many open incidents does each assignment group have?" (any table works, not just the platform ones)

Quick start

About ten minutes on a free developer instance. On a company instance, ask your ServiceNow admin for the user in step 2.

1. Get a ServiceNow instance

Sign up for a free Personal Developer Instance (PDI) — it comes with demo incidents, changes and CIs. PDIs hibernate after a few hours idle: wake yours from the developer portal before you start.

2. Create an integration user

Don't connect as admin: new instances refuse REST basic auth for it (why), and the server needs far less.

Sign in as admin and go to All › User Administration › Users › New.
User ID mcp.integration, Identity type Machine (this ticks Web service access only), and tick Internal Integration User. If your form has no Identity type, tick Web service access only yourself. Submit, then open the user again.
Set Password, and keep the password for step 3.
Roles › Edit: add itil and snc_read_only, save.

That user can read incidents, changes, problems, CMDB and aggregates, and can't change anything. Schema, update sets and writes need more: see roles.

3. Add the server to your client

You need uv (uvx runs the server without installing it). In Claude Code:

bash

read -rs SERVICENOW_PASSWORD     # paste the password; it is not shown or kept in your historyclaude mcp add servicenow \  -e SERVICENOW_INSTANCE_URL=https://devNNNNNN.service-now.com \  -e SERVICENOW_USERNAME=mcp.integration \  -e SERVICENOW_PASSWORD="$SERVICENOW_PASSWORD" \  -- uvx mcp-server-servicenow

read -rs SERVICENOW_PASSWORD     # paste the password; it is not shown or kept in your historyclaude mcp add servicenow \  -e SERVICENOW_INSTANCE_URL=https://devNNNNNN.service-now.com \  -e SERVICENOW_USERNAME=mcp.integration \  -e SERVICENOW_PASSWORD="$SERVICENOW_PASSWORD" \  -- uvx mcp-server-servicenow

Or install the Claude Code plugin, which adds the four skills as slash commands. It reads the same SERVICENOW_* variables from the shell that starts Claude Code (details):

bash

claude plugin marketplace add jschuller/mcp-server-servicenowclaude plugin install servicenow@mcp-server-servicenow

claude plugin marketplace add jschuller/mcp-server-servicenowclaude plugin install servicenow@mcp-server-servicenow

Windows (PowerShell)

Install uv with winget install astral-sh.uv, then:

powershell

$s = Read-Host 'Password' -AsSecureString$p = [Runtime.InteropServices.Marshal]::PtrToStringBSTR([Runtime.InteropServices.Marshal]::SecureStringToBSTR($s))claude mcp add servicenow -e SERVICENOW_INSTANCE_URL=https://devNNNNNN.service-now.com -e SERVICENOW_USERNAME=mcp.integration -e "SERVICENOW_PASSWORD=$p" -- uvx mcp-server-servicenow

$s = Read-Host 'Password' -AsSecureString$p = [Runtime.InteropServices.Marshal]::PtrToStringBSTR([Runtime.InteropServices.Marshal]::SecureStringToBSTR($s))claude mcp add servicenow -e SERVICENOW_INSTANCE_URL=https://devNNNNNN.service-now.com -e SERVICENOW_USERNAME=mcp.integration -e "SERVICENOW_PASSWORD=$p" -- uvx mcp-server-servicenow

VS Code (GitHub Copilot)

[Install in VS Code]

The button adds the server to your VS Code user profile and asks for the instance URL, user and password on first start, storing the password securely. Or add this to .vscode/mcp.json. Use Copilot Chat in Agent mode.

json

{  "inputs": [    { "type": "promptString", "id": "servicenow-url", "description": "ServiceNow instance URL, e.g. https://devNNNNNN.service-now.com" },    { "type": "promptString", "id": "servicenow-password", "description": "Password for mcp.integration", "password": true }  ],  "servers": {    "servicenow": {      "type": "stdio",      "command": "uvx",      "args": ["mcp-server-servicenow"],      "env": {        "SERVICENOW_INSTANCE_URL": "${input:servicenow-url}",        "SERVICENOW_USERNAME": "mcp.integration",        "SERVICENOW_PASSWORD": "${input:servicenow-password}"      }    }  }}

{  "inputs": [    { "type": "promptString", "id": "servicenow-url", "description": "ServiceNow instance URL, e.g. https://devNNNNNN.service-now.com" },    { "type": "promptString", "id": "servicenow-password", "description": "Password for mcp.integration", "password": true }  ],  "servers": {    "servicenow": {      "type": "stdio",      "command": "uvx",      "args": ["mcp-server-servicenow"],      "env": {        "SERVICENOW_INSTANCE_URL": "${input:servicenow-url}",        "SERVICENOW_USERNAME": "mcp.integration",        "SERVICENOW_PASSWORD": "${input:servicenow-password}"      }    }  }}

Claude Desktop

Edit claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

json

{  "mcpServers": {    "servicenow": {      "command": "uvx",      "args": ["mcp-server-servicenow"],      "env": {        "SERVICENOW_INSTANCE_URL": "https://devNNNNNN.service-now.com",        "SERVICENOW_USERNAME": "mcp.integration",        "SERVICENOW_PASSWORD": "your-password"      }    }  }}

{  "mcpServers": {    "servicenow": {      "command": "uvx",      "args": ["mcp-server-servicenow"],      "env": {        "SERVICENOW_INSTANCE_URL": "https://devNNNNNN.service-now.com",        "SERVICENOW_USERNAME": "mcp.integration",        "SERVICENOW_PASSWORD": "your-password"      }    }  }}

Codex, opencode, Antigravity, Cursor, pi, the Claude Code plugin and keeping the password out of config files: client setup.

4. Check it works

Ask: "List the 5 most recent incidents." The start-here user holds snc_read_only, so the server lists only the 13 read-only tools. Give the user write roles (and remove snc_read_only) and the 7 write tools appear; your client asks before each write.

No answer? Run the same configuration with --check. It makes read-only requests, prints one line per check (instance reachable, identity, roles, table read, schema, aggregates) and never prints a secret:

bash

SERVICENOW_INSTANCE_URL=https://devNNNNNN.service-now.com SERVICENOW_USERNAME=mcp.integration \  SERVICENOW_PASSWORD="$SERVICENOW_PASSWORD" uvx mcp-server-servicenow --check

SERVICENOW_INSTANCE_URL=https://devNNNNNN.service-now.com SERVICENOW_USERNAME=mcp.integration \  SERVICENOW_PASSWORD="$SERVICENOW_PASSWORD" uvx mcp-server-servicenow --check

Got an answer back? Say which client and ServiceNow release in Show and tell — it tells us what works. Questions go to Q&A.

If it doesn't work

Everything else: run --check (above), then TROUBLESHOOTING.

Tools

20 tools, 5 resources and 4 skills. Full reference: tools, resources and skills.

Group	Tools
Table API	`list_records` `get_record` `create_record` `update_record` `delete_record` `aggregate_records`
CMDB	`list_ci` `get_ci` `create_ci` `update_ci` `get_ci_relationships`
System	`get_table_schema` `get_current_user` `get_system_properties` `find_references`
Update sets	`list_update_sets` `get_update_set` `create_update_set` `set_current_update_set` `list_update_set_changes`

Resources: table schemas, instance info, the current update set, the CMDB class hierarchy and an encoded-query reference — read without a tool call.

Skills: four guided workflows for the Now Platform, served over MCP as skill:// resources so every client gets them with no plugin:

exploring-tables: schemas, choice lists, a record's history, what touches a table or field, the encoded-query reference;
analyzing-access: who holds which roles, team rosters and group members, and what a 403 or a missing field means;
reviewing-update-sets: risk categories and a pre-promotion checklist;
servicenow-cmdb: CMDB data quality and CSDM conformance.

To run with the tools only, add the server without the plugin (claude mcp add, or an mcp.json entry) and set SERVICENOW_SKILLS=off (or --skills off). off changes only what the server serves: the Claude Code plugin still loads the four skills from its own folder (configuration).

Community skills: skills for applications such as ITSM, and for your own conventions, live in their authors' repositories, each with its own eval results:

EXTENDING.md covers writing, validating, testing with mocked tools, and sharing them;
to find them, browse the servicenow-mcp-skill topic and Discussions › Skills. This project doesn't vet them.

The incident triage skill that shipped here until 0.9.0 is now an example.

Roles

ServiceNow's ACLs decide what the user can do; the server adds nothing on top.

You want	Roles	Run with
Read ITSM and CMDB data (the start-here user)	`itil` + `snc_read_only`	no flag: write tools are hidden for `snc_read_only`
…and create or update incidents and CIs	`itil` (no `snc_read_only`)	no flag; the client asks before writes (`--read-only` on clients that don't ask)
…and delete incidents, problems, changes	add `itil_admin`
Table schemas	add `personalize_dictionary`
Update sets, system properties	`admin` — on a PDI only

Per-tool detail: roles per tool. Setting up a company instance: recommended integration identity.

Safety and governance

Read-only mode — --read-only hides the 7 write tools and refuses any non-GET request.
Read-only identities see read-only tools — when the user holds snc_read_only the write tools are hidden without a flag. A convenience, not a control: ServiceNow refuses those writes anyway.
Table scope lives in ServiceNow — ACLs and REST API access policies on the integration user decide which tables and fields it can read, dot-walks included.
Audit log — one JSON line per tool call or resource read: who, which table, outcome; written fields by name only, never their values, and secret-like values in queries masked.
Your client approves writes — every tool is annotated read-only or destructive, so Claude Code, Copilot and Codex ask before a write. Clients that don't ask (opencode by default, pi) need a read-only identity, or --read-only when the identity can write.

Flags and environment variables: configuration.

Works with

Verified with 0.8.0 on 2026-10-11 against ServiceNow Brazil, and the 0.9.0 skills re-checked in Claude Code and Codex: Claude Code 2.1.296, VS Code 1.140 with GitHub Copilot, Codex CLI 0.162.1, opencode 1.19.0, Antigravity CLI 1.1.20 and pi 1.1.0. Claude Desktop, Cursor and any other client that speaks MCP over stdio or Streamable HTTP should work too; behaviour per client: client setup.

Client setup — every client, the Claude Code plugin, Windows
Configuration — the recommended identity, OAuth client credentials (headless), API keys, multiple instances, secrets, every setting
Remote deployment — from source, Streamable HTTP, OAuth 2.1 + PKCE, Docker, Cloud Run
Alongside ServiceNow's own MCP servers
Architecture and embedding — mount it in your own FastMCP server
Write your own skills — the template, the validator, the GitHub Action, sharing
Privacy — the server talks only to your instance; no telemetry
Contributing · Changelog · Support · Security

Write your own skills: EXTENDING.md covers the template, the validator and how to share them. Next: MCP prompts.

Related: sn-app-template — a ServiceNow scoped app template for Claude Code + now-sdk that pairs with this server.

License

MIT. An independent project, not affiliated with or endorsed by ServiceNow, Inc. ServiceNow is a trademark of ServiceNow, Inc.

Source: README.md at commit cac68dd

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.9.3LatestOct 29, 2026
v0.9.2Oct 21, 2026
v0.9.1Oct 13, 2026
v0.8.0Oct 12, 2026
v0.7.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts

You see	Fix
`Got HTML instead of JSON`	The PDI is asleep: wake it and retry
`401`	The user isn't Web service access only, or the password is wrong (401)
`403`	The user lacks a role for that table or tool (roles)

ServiceNow MCP Server

Overview

Installation

In SourceWeft

Other MCP clients

README

ServiceNow MCP Server

What you can ask

Quick start

1. Get a ServiceNow instance

2. Create an integration user

3. Add the server to your client

4. Check it works

If it doesn't work

Tools

Roles

Safety and governance

Works with

More

License

Tools

Version history

Score