The safe ServiceNow MCP server for developer instances and teams without Now Assist
Connect Claude Code, Cursor, or any MCP client to ServiceNow. Every table stays denied until you grant it, and it runs on a free personal developer instance with no Now Assist license.
Open source, 19 tools, and it runs on your machine with nothing listening on a port. Built by Brandon Wilson for OnlyFlows.
What is the OnlyFlows ServiceNow MCP Server?
An open-source MCP server that lets AI clients such as Claude Code and Cursor work with a ServiceNow instance through 19 tools, from record queries and schema lookups to CMDB traversal and ATF results. It runs on your machine, connects with a ServiceNow account you choose, and denies every table until a named profile grants it. It doesn't need Now Assist, so it works on personal developer instances and on instances where ServiceNow's own MCP Server isn't licensed.
Key Takeaways
- Built for developer instances and teams without Now Assist. ServiceNow's own MCP Server needs a Now Assist entitlement.
- Deny-by-default: a profile with no grants can't read or write anything.
- Setup checks your credential against the instance before saving it, and keeps it out of every client config.
- Writes are opt-in per table and per tool. Deletes need confirmation, and batch jobs dry-run first.
- 19 tools, free under the MIT License, with setup guides for Claude Code and Cursor.
Who it's for
ServiceNow developers who want an AI assistant working against a real instance, with access they control table by table.
Personal developer instances
Connect Claude Code or Cursor to your PDI and let the agent read schema, search scripts, and query records while you build. Nothing is installed on the instance.
Teams without Now Assist
ServiceNow's own MCP Server comes with Now Assist licensing. Without it, this server connects through the standard REST APIs with an account you control.
Careful first steps with AI
Start read-only on one table, then add grants one at a time. Each instance gets its own named profile, so dev and prod never share access.
Probably not the right fit if you need a remote MCP endpoint for a web-based assistant, central administration for many users, or a product ServiceNow supports. That's what ServiceNow's own MCP Server is for; the comparison below covers when to choose which.
How it keeps access narrow
Safety comes from the defaults, not from asking the model to be careful.
Denied until granted
A profile with no grants denies every call. Reads and writes are granted per table, and each grant names the tools allowed on that table.
Checked before it's saved
Setup tests your credential against the instance first, at a hidden prompt. A typo or a wrong password leaves nothing behind.
No credentials in client config
Credentials are encrypted with AES-256-GCM in an owner-only ~/.servicenow-mcp directory, or referenced from your secret manager. No MCP client config file holds one.
Local, with no open port
Your client starts the server over stdio. Nothing listens on a network port, so nothing off your machine can reach it.
Append-only incident journals
Comments and work notes have their own append-only tools, so a generic update can't overwrite a journal entry.
Destructive work is deliberate
Deletes need confirm: true and batch operations dry-run by default. Natural-language composition and ATF runs stay off until they can declare exactly what they touch.
The server acts as the ServiceNow account you connect with, and it honors any table you grant, including system tables such as sys_script. Grant the narrowest set that does the job, and connect as a user whose roles can't reach what the grant doesn't need. Sensitive-looking field names are never requested, whatever you grant.
How it compares with ServiceNow's official MCP Server
ServiceNow ships its own MCP Server through Action Fabric. It's the right choice for many licensed customers, and it solves a different problem. Requirements, cost, and tool scope side by side:
Choose the OnlyFlows server when
- You build on a personal developer instance or a sub-production instance.
- Your organization doesn't have Now Assist, or you can't spend Assists on development work.
- You work in Claude Code or Cursor and want schema, code search, and logs from the instance while you build.
- You want each instance's access denied until you grant it, table by table, on your own machine.
Choose ServiceNow's MCP Server when
- You're licensed for Now Assist and want access ServiceNow supports.
- You need a remote MCP connection, for example from a web-based assistant, with nothing installed locally.
- You want one central place to administer and govern AI access for many users.
- You want Now Assist skills, such as case and incident summarization, exposed as tools.
They aren't mutually exclusive. A common split is the OnlyFlows server against a developer instance while you build, and ServiceNow's server in a licensed production instance.
Official-server details checked in October 2026 against ServiceNow's published material. Requirements and entitlements change between releases, so confirm them with your ServiceNow account team before you plan around them.
19 Tools. Scoped to What You Grant.
Each tool works only on tables the selected profile grants, and every call names that profile.
Core CRUD
Read and write the tables a profile has been granted. Incident journals have their own append-only tools.
Query
Query an approved table with structured filters, field selection, pagination, and sorting. Raw encoded queries are opt-in per tool and table.
sn_queryGet Record
Retrieve a single record by sys_id from an approved table, with bounded default field selection.
sn_getCreate
Create a record on a table granted for writes, using only field-policy-approved writable fields. Journal fields are rejected.
sn_createUpdate
Update one record selected by exact sys_id on a table granted for writes, using only field-policy-approved writable fields.
sn_updateAdd Comment
Append one bounded customer-visible comment to an incident. Append-only: repeated calls append again.
sn_incident_add_commentAdd Work Note
Append one bounded internal work note to an incident. Append-only: repeated calls append again.
sn_incident_add_work_noteDelete
Delete a record on an approved write table. Requires an explicit confirm: true.
sn_deleteBatch
Bulk update or delete behind a required structured filter. Dry-run by default; confirm: true to execute.
sn_batchAnalytics & Schema
Counts, groupings, and table structure without exporting records.
Aggregate
COUNT, AVG, MIN, MAX, and SUM with grouping.
sn_aggregateSchema
Field definitions, types, and references for a table.
sn_schemaHealth
Instance version, cluster nodes, stuck jobs, and key stats in a single call.
sn_healthCMDB & Operations
Configuration items, files, logs, and the scripted surface of the instance.
Relationships
CMDB CI graph traversal: upstream, downstream, or both, with configurable depth.
sn_relationshipsAttachments
List attachments, download as inline base64, and upload inline base64 content. Never touches a host filesystem path.
sn_attachSystem Logs
Query system logs with severity, source, and time filters.
sn_syslogCode Search
Search business rules, script includes, client scripts, and other script records.
sn_codesearchDiscover
Discover tables, scoped apps, store apps, and plugins on the instance.
sn_discoverTesting & Automation
Shipped, and deliberately conservative: execution paths fail closed until they can declare a complete typed access plan.
ATF
List ATF tests and suites and read their results. run and run-suite currently fail closed.
sn_atfNatural Language
Natural-language composition. Currently fails closed until it emits a complete typed access plan.
sn_nlProfiles
Inspect a connection without exposing its credential.
Profile
Inspect non-secret metadata for one explicitly named profile. Profiles are created and changed outside the chat.
sn_profilesn_script shipped in 1.0 as an unimplemented stub and is not published in 2.x. It does not appear in tools/list.
Quick start
One install and one wizard. Requires Node.js 20 or newer.
Install and run setup
servicenow-mcp-setup walks through one connection: instance, credential, a live check against that instance, table grants, and client registration. By default it grants reads on incident and no writes.
npm install -g @onlyflows/servicenow-mcpservicenow-mcp-setupnpx @onlyflows/servicenow-mcp@latest setupGrant only the tables you need
Grants are additive and validated when you run them. A write grant allows create and update only; delete, batch, and ATF tools must be named with --tools.
servicenow-mcp-setup grant --profile dev --read incident,problem --write incidentRegister your MCP client
Setup registers Claude Code and Codex automatically when their CLI is on PATH. By hand:
claude mcp add --scope user servicenow-mcp -- servicenow-mcpFile-configured clients such as Cursor, Claude Desktop, and Windsurf get a command to start, with no credentials in the file:
{
"mcpServers": {
"servicenow-mcp": { "command": "servicenow-mcp", "args": [] }
}
}Ask, naming the instance
Restart your client and name the profile in the ask: “on dev, show me today's P1 incidents.” If anything looks off, the doctor prints a remedy for each failure:
servicenow-mcp-setup doctor --profile devSetup guides
Step by step, read-only first, with fixes for the errors people actually hit.
Claude Code + ServiceNow
Connect Claude Code to a free ServiceNow developer instance with the OnlyFlows MCP server. Read-only first, deny-by-default, with fixes for common errors.
Cursor + ServiceNow
Connect Cursor to a free ServiceNow developer instance with the OnlyFlows MCP server. Read-only first, deny-by-default, with fixes for common errors.
ServiceNow MCP without Now Assist
ServiceNow's official MCP Server needs Now Assist and a recent patch. What it requires, how to check your instance, and how to use MCP without it.
Works with the clients you already use
Every supported client speaks stdio, so each one is configured the same way: a command to start.
Codex
Registered automatically by setup when its CLI is on PATH
Claude Desktop
Configured in claude_desktop_config.json
VS Code
Configured in .vscode/mcp.json with "type": "stdio"
Windsurf
Configured in ~/.codeium/windsurf/mcp_config.json
What you can ask
Describe what you need and which instance you mean. The client picks the tool and passes the profile.
“On pdi, what fields are on change_request?”
Calls sn_schema with profile: "pdi". The profile must already grant reads on change_request.
“On pdi, find business rules that reference GlideRecord('incident')”
Searches business rules, script includes, and client scripts with sn_codesearch.
“On dev, add a work note to INC0010001 explaining the rollback”
Calls sn_incident_add_work_note with profile: "dev". It only appends, so nothing already on the journal can be overwritten.
“On prod, how many open incidents are there, grouped by priority?”
Runs sn_aggregate with a COUNT and a group-by, so no records leave the instance.
“On prod, show upstream dependencies for email-server-01”
Walks the CMDB relationship graph with sn_relationships at a configurable depth.
Release notes
The current release is 2.1.0. 2.0 replaced a single connection configured from environment variables with named profiles and an access boundary that fails closed.
What changed in 2.1
- sn_create and sn_update now write to any table a profile grants for writes. In 2.0 they were confined to incident, so review each profile's write grants before you upgrade.
- Each kind of policy denial has its own error message and audit reason, so a rejected value is no longer reported as a table denial.
What changed in 2.0
- Named profiles for dev, test, prod, and PDI, with credentials encrypted at rest.
- Deny-by-default table access. In 1.0 a tool could reach any table the credential could.
- OAuth 2.0 (client_credentials and password grants) and API keys, alongside basic authentication.
- servicenow-mcp-setup, a guided setup with a doctor command that prints a fix for each failure.
- Append-only incident comment and work note tools, and token-efficient responses with bounded field selection.
Upgrading from 1.0
Two changes apply to every install: name a profile on every tool call, and grant table access. Everything else only matters if you used the affected feature.
Every tool call must name a profile. There is no default, active, or session-selected profile. Set SN_PROFILE_NAME if you configure from bare SN_* variables.
Table access is deny-by-default per profile. Grant it with servicenow-mcp-setup grant before your first call.
sn_attach no longer accepts host filesystem paths. Uploads take content_base64 and downloads return inline base64.
sn_script is withdrawn. It was never functional in 1.0; use sn_query and sn_batch instead.
sn_update, sn_create, and sn_batch reject generic comments and work_notes and point to the dedicated incident journal tools.
The transport is unchanged. A client entry that started the package in 1.0 still starts it.
ServiceNow MCP FAQs
Answers for developers evaluating the server, comparing it with ServiceNow's own, or upgrading from 1.0.
Open source, MIT licensed
Built with the official MCP TypeScript SDK and maintained by Brandon Wilson, founder of OnlyFlows and a ServiceNow Certified Technical Architect. Bug reports and pull requests are welcome on GitHub.
Related
Browse ServiceNow flows, subflows, and scripts to explore with your assistant, or read up on the protocol itself.
Try it on your developer instance
One install, read-only to start, and 19 tools when you're ready to grant them.
Need help with MCP or ServiceNow AI? Contact OnlyFlows