ServiceNow MCP

1. "Where is this field actually used?"— every script, business rule, client script, UI policy/action and ACL that touches it, as JSON or a Mermaid graph. The IDE-gradefind usagesServiceNow has no button for:

// servicenow_where_used { "kind": "field", // "table" | "field" | "script" "name": "u_cost_center", "mermaid": true, // also render a reference graph }

2. "What runs when I save this record?"— the full automation chain in execution order (display → before → after → async business rules, then flows, workflows and notifications), each with its condition — a logical test that runsnothing:

// servicenow_trace_table_event { "table": "incident", "operation": "update", // insert | update | delete | query }

3. "What drifted between dev and prod?"— a Markdown diff of tables, columns, scripts (by SHA-256) and plugins between two configured profiles, with a CI-friendly exit code so a pipeline can block a risky deploy:

servicenow-mcp-ai drift dev prod # report on stdout; exit 1 on drift, 0 if clean

All three areread-onlyand work against any instance — including a free PDI — with the model and client of your choice.

- FullTable API: query, read, create, update and delete records onanytable, with encoded queries, field selection and pagination.
- Extra ServiceNow APIs:Aggregate(Stats),Attachment(list/upload/download/delete),Import Set,Batch(many REST calls in a single request), plus table/columnmetadata(sys_db_object,sys_dictionary).
- Process & plugin APIs:CMDB(class-aware CI CRUD + meta via IRE),Service Catalog(browse/order items),Change Management(typed creation + conflict detection) andKnowledge(article search). Plugin-scoped APIs report clearly when not active on the instance.
- Script intelligence: read and search the instance's own code (business rules, script includes, client scripts, UI policies/actions, scheduled jobs, transform/REST scripts, ACLs) and get a table's full automation picture — all read-only over the Table API.
- Flow tracing & code checking(Phase 8): deterministically trace what a table operation runs (flowspackage — business rules, flows, workflows and notifications, in order, with a Mermaid flowchart), read Flow Designer flows and run history, and lint scripts against a local rule set with an aggregate code-health report (codecheck). Run ATF tests via the CI/CD API (atf, opt-in, non-default — the run tools execute on the instance).
- Self-documentation: a local Markdown knowledge base (read/write/search) plus deterministic Mermaid generators (ER diagrams from references, record-lifecycle flowcharts from business rules) so the server builds durable, reusable context.
- Prompts: ready-made workflows (incident triage, change impact analysis, document a table) that orchestrate the tools.
- Tool packages: load only the tool groups you need viaSN_TOOL_PACKAGES(default profilecore;allenables everything).
- BasicorOAuth 2.0authentication over HTTPS; the password/token is never echoed back.
- Least-privilege controls: table allow/deny lists and a global read-only mode.
- Resilience: per-request timeout, retry with backoff andRetry-After, SSRF guard, and a result-size guard.
- MCPtool annotationsandresources, structured error payloads, and structured logging on stderr.
- Credentials in an env file (project,~/.config, orSN_ENV_FILE), updatable at runtime viaservicenow_set_credentials.

- Node.js 20+ (enforced:engines+ a runtime guard with a clear message; the project targets the version in.nvmrc).

Or run the published package directly, without cloning:

Register it with an MCP client (Claude Desktop, VS Code Chat, the Inspector…) by pointing the server command atnpx:

Credentials are read from~/.config/servicenow-mcp-ai/.env(or real environment variables) — see below.

The fastest path is three lines of Basic auth — set these (in the env file or the real environment) and you are connected:

SN_INSTANCE=dev12345.service-now.com SN_USER=your.username SN_PASSWORD=your-password

Once the three variables are set, confirm the connection before you start:
- Run theservicenow_test_connectiontool — it reads onesys_userrecord and reportsok, HTTP status and latency.
- Runservicenow_check_capabilities— it previews which admin-restrictedsys_tables the connected user can actually read.

npx servicenow-mcp-ai doctor # checks credentials, reachability and capabilities

SN_INSTANCE=your-instance.service-now.com SN_USER=your.username@example.com SN_PASSWORD=your-password

drifttakes two positional profile names; each must resolve to a configured profile (SN_PROFILE_<NAME>_, or the bareSN_INSTANCE/SN_USER/SN_PASSWORDkeys fordefault). The Markdown report is written tostdout(capture it as a CI artifact); a one-line drift summary goes to stderr.

Compare two configured profiles andfail a pipeline on configuration drift:

servicenow-mcp-ai drift dev prod # report on stdout; exit 1 on drift, 0 if clean, 2 on error

npm run check # full gate: build, lint, format check, coverage-gated tests, prod audit npm test # unit tests only (node:test; needs a prior npm run build) npm run lint # ESLint (flat config + typescript-eslint) npm run format # format with Prettier

This table is generated from the tool registrations — edit the tool definitions insrc/tools/, then runnpm run docs:readme.

All tools carry MCP annotations (readOnlyHint,destructiveHint,idempotentHint) so clients can apply the right confirmation UX.

Tools are grouped into packages so you can expose only what a given client needs (fewer tools keep the model focused). SetSN_TOOL_PACKAGESto a comma/space separated list of profiles or package names:

- core(default) —table,schema,aggregate,attachment.
- all— every package below.
- Individual packages:table,schema,aggregate,attachment,importset,batch,catalog,change,knowledge,cmdb,scripts,flows,codecheck,docs,instance,email,atf.

The admin tools (servicenow_set_credentials,servicenow_get_status) are always registered, regardless of the active packages. Unknown names are ignored.servicenow_get_statusreports the resolvedenabledPackages.

# Only table + batch tools (plus the always-on admin tools) SN_TOOL_PACKAGES=table,batch

If you would rather not curate the list yourself, three named presets cover the common roles. The admin tools are always on, so they are not listed. Each preset also has a one-word alias —SN_TOOL_PACKAGES=reader|developer|admin— that expands to the same package set.

Thedeveloperpreset builds on thereaderset; thedocspackage includes the Mermaid diagram generators. Use the alias for brevity or spell the packages out to add or drop one.

Query the 5 most recent active incidents:

- The env file is git-ignored — do not commit real credentials.
- The env file is writtenowner-only (0600)— it holds a plaintext password.
- The server uses the stdio transport and only logs tostderr; secrets and raw encoded queries are never logged.
- The password/token is never returned by any tool.
- Hosts are restricted: withoutSN_ALLOWED_HOSTS, only*.service-now.cominstances are contacted (internal/loopback always blocked), so a redirected or mistyped host cannot silently receive credentials. SetSN_ALLOWED_HOSTSto opt in a custom or sovereign-cloud domain.
- PreferOAuth 2.0over Basic where possible (SN_OAUTH_CLIENT_ID).
- Apply least privilege withSN_TABLES_ALLOW/SN_TABLES_DENYandSN_READONLY=truefor read-only deployments.
- Table policy does not cover plugin APIs.SN_TABLES_DENY=change_requestblocks the Table API path, but the Change Management API (sn_chg_rest) can still read/write changes. To restrict the plugin-backed surfaces useSN_PACKAGES_DENY(drop the whole package) orSN_PACKAGES_READONLY(register only its read tools). The Batch API obeys both axes too: a sub-request to a denied package's path is refused, and writes to a read-only package are blocked — a batch cannot be used to bypass the package policy.

This project is built and maintained in my own time. If it saves you or your team time, please consider supporting its continued development — sponsorship directly funds new tools, bug fixes and keeping pace with ServiceNow's REST surface.

servicenow-mcp-aiis an independent, community-built project. It isnot affiliated with, endorsed by, or sponsored by ServiceNow, Inc.

"ServiceNow", the ServiceNow logo, "Now", and related marks are trademarks or registered trademarks of ServiceNow, Inc. in the United States and other countries. They are used in this project's name and documentationonly nominatively— to identify the platform this software interoperates with — and no affiliation or endorsement is implied. All other product names and marks are the property of their respective owners.

MCP Server for Kingdee K3Cloud (金蝶云星空) — one of the most widely used ERP systems in China. Connects AI assistants (Claude Desktop, Cursor, Cline, Cherry Studio, etc.) to Kingdee ERP via natural language.

Generate documents, process PDFs, and manage e-signature workflows using the PDFGate API.