ServiceNow MCP server — 67 tools over the full REST surface, every auth method, flows, diagrams.
ServiceNow MCP server — 67 tools over the full REST surface, every auth method, flows, diagrams. The servicenow mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
Everything the assistant can do here goes through one of these:
Self-documentation — a local Markdown knowledge base (read/write/search) plusPrompts — ready-made workflows (incident triage, change impact analysis,Least — privilege controls: table allow/deny lists and a global read-only modeResilience — per-request timeout, retry with backoff and Retry-After, SSRFMethod — SN_AUTHBasic — basicVariable — RequiredSN_INSTANCE — yesSN_USER — yesSN_PASSWORD — yesSN_TIMEOUT_MS — noSN_MAX_RETRIES — noInstallation goes through your MCP client rather than a global install: point it at servicenow-mcp-ai on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
You will need 8 environment variables: SN_OAUTH_CLIENT_ID, SN_OAUTH_CLIENT_SECRET, SN_OAUTH_REFRESH_TOKEN, SN_OAUTH_JWT_KEY, SN_API_KEY, SN_BEARER_TOKEN, SN_TLS_CLIENT_KEY, SN_HTTP_HOST. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
engines + a runtime guard with a clear message; the project targets the version in .nvmrc).Plenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Servicenow's toolset — Self-documentation, Prompts, Least and 11 more — is a fair guide to whether it matches your workflow. It is maintained by IvanBBaev; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Self-documentation | a local Markdown knowledge base (read/write/search) plus |
| Prompts | ready-made workflows (incident triage, change impact analysis, |
| Least | privilege controls: table allow/deny lists and a global read-only mode. |
| Resilience | per-request timeout, retry with backoff and Retry-After, SSRF |
| Method | SN_AUTH |
| Basic | basic |
| Variable | Required |
| SN_INSTANCE | yes |
| SN_USER | yes |
| SN_PASSWORD | yes |
| SN_TIMEOUT_MS | no |
| SN_MAX_RETRIES | no |
| SN_MAX_RECORDS | no |
| SN_MAX_RESULT_CHARS | no |
{
"mcpServers": {
"servicenow-mcp-ai": {
"command": "npx",
"args": ["-y", "servicenow-mcp-ai"],
"env": {
"SN_OAUTH_CLIENT_ID": "your-value",
"SN_OAUTH_CLIENT_SECRET": "your-value",
"SN_OAUTH_REFRESH_TOKEN": "your-value",
"SN_OAUTH_JWT_KEY": "your-value",
"SN_API_KEY": "your-value",
"SN_BEARER_TOKEN": "your-value",
"SN_TLS_CLIENT_KEY": "your-value",
"SN_HTTP_HOST": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
engines + a runtime guard with a clear message; the project targets the version in .nvmrc).| Variable | Description | Required |
|---|---|---|
| SN_OAUTH_CLIENT_ID | Configuration value read at startup. | Optional |
| SN_OAUTH_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| SN_OAUTH_REFRESH_TOKEN | Credential the server authenticates with. | Yes |
| SN_OAUTH_JWT_KEY | Credential the server authenticates with. | Yes |
| SN_API_KEY | Credential the server authenticates with. | Yes |
| SN_BEARER_TOKEN | Credential the server authenticates with. | Yes |
| SN_TLS_CLIENT_KEY | Credential the server authenticates with. | Yes |
| SN_HTTP_HOST | Endpoint or connection string the server talks to. | Optional |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.