Skip to main content
Glama
ServiceNow MCP Server

ServiceNow MCP Server

by jschuller

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)

Related MCP server: ServiceNow MCP Server

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.

  1. Sign in as admin and go to All › User Administration › Users › New.

  2. 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.

  3. Set Password, and keep the password for step 3.

  4. 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:

read -rs SERVICENOW_PASSWORD     # paste the password; it is not shown or kept in your history
claude 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):

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

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

$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

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.

{
  "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}"
      }
    }
  }
}

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

{
  "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:

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

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)

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:

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.

More

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.

Available Tools

20 tools
aggregate_recordsAggregate RecordsA
Read-onlyIdempotent

Aggregate records using COUNT, AVG, MIN, MAX, SUM with optional GROUP BY via the Stats API.

If the Stats API is refused (401) while list_records works, count with list_records instead: the same query, fields="sys_id", limit=1000, paging with offset.

Inputs: table_name (required), count, query, having, +6 more.

create_ciCreate CiA

Create a new CMDB configuration item

Inputs: data (required), class_name.

create_recordCreate RecordB

Create a new record in any ServiceNow table

Inputs: data (required), table_name (required).

create_update_setCreate Update SetA

Create a new update set for tracking customizations

Inputs: name (required), parent, description.

delete_recordDelete RecordB
DestructiveIdempotent

Delete a record from a ServiceNow table by sys_id

Inputs: sys_id (required), table_name (required).

find_referencesFind ReferencesA
Read-onlyIdempotent

Where-used for a table or one of its fields: the business rules, client scripts, UI policies, ACLs, script includes and reference fields that touch it.

Returns names, sys_ids and flags only, never script, condition or ACL bodies. Script matches (script includes; business rules and client scripts in field mode) are text matches, so expect false positives. Only this exact table is matched: run it again for a parent table (get_table_schema's hierarchy) to find rules and ACLs defined there. A source this identity can't read (403, or a 401 from an access policy that leaves its table out) is listed in not_assessable (under OAuth each such source costs one token refresh). Under basic auth the first 401 is an error (a refused password looks the same), and so is a refused OAuth secret; rows hidden by an ACL are simply missing. complete=false means the source hit the limit.

Inputs: table_name (required), limit, field_name. Returns: note, field, table, groups, +2 more

get_ciGet CiB
Read-onlyIdempotent

Get a single CMDB configuration item by sys_id

Inputs: sys_id (required), class_name, display_value.

get_ci_relationshipsGet Ci RelationshipsB
Read-onlyIdempotent

Get relationships for a CMDB configuration item (parent and child)

Inputs: sys_id (required), limit, offset, relation_type. Returns: note, count, truncated, next_offset, +1 more

get_current_userGet Current UserA
Read-onlyIdempotent

Get the authenticated user's identity and directly assigned, active roles

Inputs: fields.

get_recordGet RecordA
Read-onlyIdempotent

Get a single record from a ServiceNow table by sys_id.

If this is refused (401) while list_records works, call list_records with query="sys_id=<sys_id>" and limit=1 instead.

Inputs: sys_id (required), table_name (required), fields, display_value.

get_system_propertiesGet System PropertiesC
Read-onlyIdempotent

Query ServiceNow system properties

Inputs: limit, query. Returns: note, count, truncated, properties

get_table_schemaGet Table SchemaA
Read-onlyIdempotent

Get the data dictionary (field definitions) for a ServiceNow table, including inherited fields

Inputs: table_name (required), limit, include_inherited. Returns: note, table, fields, hierarchy, +2 more

get_update_setGet Update SetA
Read-onlyIdempotent

Get details of a specific update set by sys_id

Inputs: sys_id (required).

list_ciList CiB
Read-onlyIdempotent

List CMDB configuration items with optional class and query filtering

Inputs: limit, query, fields, offset, +3 more. Returns: note, class, count, records, +4 more

list_recordsList RecordsB
Read-onlyIdempotent

List records from any ServiceNow table with optional filtering, field selection, and pagination

Inputs: table_name (required), limit, query, fields, +4 more. Returns: note, count, records, warning, +3 more

list_update_set_changesList Update Set ChangesC
Read-onlyIdempotent

List all customer updates (changes) within an update set

Inputs: update_set_sys_id (required), limit. Returns: note, count, changes, truncated

list_update_setsList Update SetsB
Read-onlyIdempotent

List update sets with optional state and query filtering

Inputs: limit, query, state. Returns: note, count, truncated, update_sets

set_current_update_setSet Current Update SetA
Idempotent

Set an update set as the current active update set

Inputs: sys_id (required).

update_ciUpdate CiC
DestructiveIdempotent

Update a CMDB configuration item

Inputs: data (required), sys_id (required), class_name.

update_recordUpdate RecordC
DestructiveIdempotent

Update an existing record in a ServiceNow table

Inputs: data (required), sys_id (required), table_name (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation3/5

    The generic record tools overlap substantially with the CI-specific tools: create_record/create_ci, update_record/update_ci, list_records/list_ci, and get_record/get_ci all target the CMDB table in different ways. Descriptions clarify the CMDB intent, but an agent must still decide whether to use the generic or specialized tool for the same underlying table.

    Naming Consistency5/5

    All tool names use consistent snake_case and a verb_noun pattern such as create_record, list_records, get_update_set, and delete_record. The few compound names like set_current_update_set and get_ci_relationships remain predictable and readable.

    Tool Count3/5

    Twenty tools is at the high end for a single MCP server and feels heavy, though the broad ServiceNow surface area (records, CMDB, update sets, metadata) explains much of the count. It is reasonable but not tightly scoped.

    Completeness4/5

    Core record CRUD is complete, and CMDB plus update-set workflows are mostly covered with schema, references, aggregation, and current-user tools. Minor gaps exist, such as no dedicated delete_ci or broader update-set lifecycle operations, but generic record tools can cover some of these.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      C
      quality
      D
      maintenance
      Enables Claude to interact with ServiceNow instances through comprehensive API integration. Supports incident management, service catalog operations, change requests, knowledge base management, user administration, and agile project management with multiple authentication methods.
      82
      MIT