Servicenow MCP AI runs on your own machine — the client starts it, so there is no endpoint to ping. 681 installs a week from npm. Last commit 31 Oct 2026.
ServiceNow MCP server — 67 tools over the full REST surface, every auth method, flows, diagrams.
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
пакет servicenow-mcp-ai ссылается на ivanbbaev/servicenow-mcp-ai
const child = spawn(launch.command, launch.args, {
new Function(source);
sysId ? `an update of ${sysId}` : "a create"
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add servicenow-mcp-ai -e 'SN_INSTANCE=<SN_INSTANCE>' -- npx -y servicenow-mcp-ai
{
"mcpServers": {
"servicenow-mcp-ai": {
"command": "npx",
"args": [
"-y",
"servicenow-mcp-ai"
],
"env": {
"SN_INSTANCE": "<SN_INSTANCE>"
}
}
}
}
[mcp_servers.servicenow-mcp-ai]
command = "npx"
args = ["-y", "servicenow-mcp-ai"]
env = { SN_INSTANCE = "<SN_INSTANCE>" }
{
"mcpServers": {
"servicenow-mcp-ai": {
"command": "npx",
"args": [
"-y",
"servicenow-mcp-ai"
],
"env": {
"SN_INSTANCE": "<SN_INSTANCE>"
}
}
}
}
{
"servers": {
"servicenow-mcp-ai": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"servicenow-mcp-ai"
],
"env": {
"SN_INSTANCE": "<SN_INSTANCE>"
}
}
}
}
Put your own value in place of
<SN_INSTANCE> (ServiceNow instance host, e.g. dev12345.service-now.com).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
SN_AUTH (Auth mode: basic | oauth | apikey | token | none. Auto-detected from the keys present if omitted), SN_USER (Username for basic auth or the OAuth password grant), SN_PASSWORD (Password for basic auth or the OAuth password grant), SN_API_KEY (ServiceNow API key, sent as the x-sn-apikey header (apikey auth)), SN_TOOL_PACKAGES (Which tool packages to expose, e.g. core (default), all, or a comma-separated list).
Git/CI MCP server with the full protocol surface (tools, resources, prompts, roots, sampling).
Multi-instance ServiceNow MCP server with 40+ tools and intelligent schema discovery
Build and operate declarative REST/Kafka services on Orion: 58 tools over the full admin API.
Measure MCP servers, pin the approved tool surface, refuse calls to tools that changed. Local-first.
Raycast workflow automation MCP server with 9 tools
Multi-account Google Workspace MCP server: 942 tools, 29 services, discover-first, BYO OAuth.
MCP server for the Rise of Machine AI tools directory.
Free proof-of-existence attestation for digital files, MCP tools for the imgauth service.
Answers built from our own checks of this server.