Guide: requirements and alternatives

    ServiceNow MCP without Now Assist: requirements and alternatives

    ServiceNow's own MCP Server needs Now Assist or Prime licensing and a recent Zurich or Australia patch. If you don't have that, or you're on a personal developer instance, you can still connect Claude, Cursor, or another MCP client through a server that uses ServiceNow's REST APIs with your own account.

    Updated Tested with @onlyflows/servicenow-mcp 2.1.08-minute read, plus about 20 minutes to set up
    Quick Answer

    Yes, you can use MCP with ServiceNow without Now Assist. ServiceNow's MCP Server Console requires a Now Assist entitlement, but community MCP servers such as the OnlyFlows server connect through the standard REST APIs with an ordinary ServiceNow account. That works on any instance you can reach, including a free personal developer instance. The trade-off is that you run the server yourself, and ServiceNow doesn't support it.

    What you need

    • For the official server: a Now Assist entitlement (or Prime licensing), a supported release, and an admin who can install store apps and create OAuth clients.
    • For the OnlyFlows server: Node.js 20 or newer on your machine, an MCP client, and a ServiceNow account that can use the REST API.

    Safe defaults

    • Start on a developer or sub-production instance, not production.
    • Connect as a dedicated integration user with narrow roles, not admin.
    • Grant reads first. The OnlyFlows setup wizard grants reads on incident and no writes by default.
    • Treat any community server as code you run with your credentials: check what a fresh install can reach and where it keeps secrets.

    What ServiceNow's official MCP Server requires

    ServiceNow launched its MCP Server at Knowledge 2026 as part of Action Fabric, and includes it in Now Assist and AI Native SKUs. You administer it in MCP Server Console. Based on ServiceNow's published material as of October 2026, you need:

    • A recent release. ServiceNow's guidance names Zurich Patch 9 or Australia Patch 2 as the minimum for MCP Server Console.
    • A Now Assist entitlement for the domain you want to expose, such as ITSM or ITOM, or Prime licensing. ServiceNow staff describe the ready-made servers as requiring Assists from Now Assist packs or Prime, so tool calls draw on that allowance.
    • The MCP Server Console store app, activated through the Now Assist application.
    • An OAuth client on the instance for each MCP client that connects. Clients connect to the instance remotely; there's no local server to run.
    • Tools to expose. A Quickstart server comes preconfigured with incident and case tools. Ready-made ITSM, ITOM, CMDB, and SPM servers became generally available on 10 September 2026, and you can build more tools in the console, including from Now Assist skills.

    What about personal developer instances?

    ServiceNow hasn't published a policy on MCP Server Console for personal developer instances. Community reports say the plugins show as unavailable on a PDI, because PDIs don't carry a Now Assist entitlement. To experiment with MCP on a PDI today, a community server is the practical route.

    How to check whether your instance qualifies

    Three checks tell you whether the official route is open to you:

    • Release and patch. Open stats.do on the instance. The build tag shows the release family and patch level.
    • Entitlement. Ask your ServiceNow admin or account team whether your subscription includes Now Assist for the domain you need, or Prime licensing.
    • The store app. Look for MCP Server Console in the ServiceNow Store or your instance's application manager. If your instance can't install it, the entitlement isn't there yet.

    Alternatives that don't need Now Assist

    Without the entitlement, these are the realistic options, from the least to the most work:

    • The OnlyFlows ServiceNow MCP server. Free and MIT licensed. It runs on your machine over stdio, has 19 tools, and denies every table until you grant it. It works with Claude Code, Cursor, Codex, VS Code, Claude Desktop, and Windsurf. See the product page.
    • Another open-source server. 327 GitHub repositories matched “servicenow mcp” in October 2026, including echelon-ai-labs/servicenow-mcp and aartiq's NowAIKit, which advertises more than 500 tools. Before you point one at a real instance, check what a fresh install can reach and where it keeps your credential.
    • A direct REST integration. If one fixed workflow is all you need, a purpose-built script against the Table API can be simpler than any MCP server. Compare the two approaches.
    • A Now Assist trial. ServiceNow invites customers to try the ready-made MCP servers with their own data through their account team.

    OnlyFlows vs ServiceNow's MCP Server

    Best for
    OnlyFlows: Developers on personal developer instances (PDIs) and sub-production instances, and teams without Now Assist.
    Official: Customers licensed for Now Assist who want ServiceNow-managed MCP access, including in production.
    Instance requirements
    OnlyFlows: Any instance you can reach with a REST API credential, including a free PDI. Nothing is installed on the instance.
    Official: The MCP Server Console store app, activated through Now Assist. ServiceNow's guidance names Zurich Patch 9 or Australia Patch 2 as the minimum release.
    License and cost
    OnlyFlows: Free and open source under the MIT License. Calls count against your instance's normal REST API limits.
    Official: Included with Now Assist or Prime licensing. Tool calls draw on your Assist allowance.
    Where it runs
    OnlyFlows: On your machine. Your MCP client starts it over stdio, and nothing listens on a port.
    Official: On your instance. MCP clients connect to it remotely and authenticate with OAuth.
    Tool scope
    OnlyFlows: 19 tools: record CRUD, append-only incident journals, aggregates, schema, CMDB relationships, attachments, system logs, code search, discovery, and ATF results.
    Official: A Quickstart server with preconfigured incident and case tools, ready-made ITSM, ITOM, CMDB, and SPM servers (generally available since 10 September 2026), and tools you build in MCP Server Console, including from Now Assist skills.
    Access control
    OnlyFlows: Every table is denied until a named profile grants it, checked before any request leaves your machine. ServiceNow ACLs still apply to the account you connect as.
    Official: Configured centrally on the instance, with ServiceNow roles and ACLs and governance through AI Control Tower.
    MCP clients
    OnlyFlows: Local clients that can start a command: Claude Code, Cursor, Codex, VS Code, Claude Desktop, and Windsurf.
    Official: Remote clients that support OAuth. ServiceNow names Claude, Copilot, and Gemini as examples.
    Support
    OnlyFlows: Community support through GitHub issues. Not supported by ServiceNow.
    Official: Supported by ServiceNow under your subscription.

    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.

    Set up the OnlyFlows server, read-only first

    1. 1

      Install the server

      Check that node --version prints v20 or newer, then install the package globally so your MCP client can start the servicenow-mcp command.

      npm install -g @onlyflows/servicenow-mcp
    2. 2

      Run setup and keep the read-only defaults

      The wizard asks for a profile name, your instance, and a credential, checks the credential against the instance before saving anything, then asks which tables to grant. Name the profile pdi (any name works; the examples below use it) and keep the default grants: reads on incident, no writes.

      If your instance refuses basic authentication for API calls, choose oauth and create an OAuth API endpoint client under System OAuth > Application Registry first.

      servicenow-mcp-setup
    3. 3

      Connect your MCP client

      Setup registers Claude Code and Codex automatically when their commands are on your PATH. To do it by hand:

      Claude Code

      claude mcp add --scope user servicenow-mcp -- servicenow-mcp

      Codex

      codex mcp add servicenow-mcp -- servicenow-mcp

      Cursor (~/.cursor/mcp.json), Claude Desktop, and Windsurf

      {
        "mcpServers": {
          "servicenow-mcp": { "command": "servicenow-mcp", "args": [] }
        }
      }

      Print the entry for every supported client, VS Code included

      servicenow-mcp-setup client --client all

      Step-by-step versions: Claude Code and Cursor.

    4. 4

      Check the connection

      Run the doctor, then ask your assistant for a bounded read that names the profile, such as “On pdi, show me the five most recent incidents.”

      servicenow-mcp-setup doctor --profile pdi

    Troubleshooting

    Start with servicenow-mcp-setup doctor: it checks the install end to end and prints a remedy for each failure. These are the errors people hit most often.

    Your client can't start the server.

    Cause: The servicenow-mcp command isn't on the PATH your client runs with, which is common with nvm or GUI apps.

    Fix: Run servicenow-mcp-setup doctor. If the server command check fails, register the server by absolute path as the doctor suggests. The Claude Code and Cursor guides show the exact entries.

    Every tool call fails with “Table access was denied by policy.”

    Cause: The profile has no grant for that table or tool. The other common cause: SN_ALLOWED_READ_TABLES or SN_ALLOWED_WRITE_TABLES is set in your environment while a profile file exists. Those variables only apply when there is no profile file.

    Fix: Grant the table on the profile, then restart your MCP client so it starts a fresh server. servicenow-mcp-setup doctor reports both causes.

    servicenow-mcp-setup grant --profile pdi --read incident

    Setup says the instance “has no Table API at the expected path (HTTP 404)” or “did not respond before the timeout”.

    Cause: The developer instance is hibernating, or the host name has a typo.

    Fix: Wake the instance from developer.servicenow.com, wait until it loads in a browser, and run setup again. Enter just the host, such as dev12345.service-now.com.

    Setup says the instance “rejected the credential (HTTP 401)”.

    Cause: The username or password is wrong, the account is locked or waiting on a password reset, or the instance is enforcing ServiceNow's basic authentication restrictions for API calls (KB3096078).

    Fix: Check the credential and the account's status. If the account is fine but API calls are refused, tick Web service access only on the user, give it the snc_basic_auth_api_access role, or switch the profile to OAuth.

    Setup says the instance “accepted the credential but denied reading incident (HTTP 403)”.

    Cause: The account signed in, but its ServiceNow roles don't allow reading incident.

    Fix: Give the user a role that can read the tables you grant, such as itil. A table grant in the MCP server never widens what ServiceNow's ACLs allow.

    Tool calls return an authentication error, although setup worked.

    Cause: The server couldn't resolve the stored credential. An encrypted credential needs the SN_PROFILE_ENCRYPTION_KEY that setup wrote to ~/.servicenow-mcp/server.env. If that file is deleted or replaced, the credential can't be decrypted.

    Fix: Run servicenow-mcp-setup doctor --profile pdi and follow the remedy it prints. Don't delete server.env; servicenow-mcp-setup --force regenerates the other identifiers but keeps the key. If the key is gone, re-enter the credential with servicenow-mcp-profile rotate --name pdi --field credential.

    A grant you just added has no effect.

    Cause: your MCP client started the server before you changed the profile, and the server reads the profile when it starts.

    Fix: Restart your MCP client so it starts a fresh server.

    Still stuck? Open an issue on GitHub with the doctor's output. It never prints a secret.

    FAQ

    Sources

    Details about ServiceNow's MCP Server were checked on 24 October 2026. Requirements and entitlements change between releases, so confirm them with your ServiceNow account team.