This profile is part of our MCP server directory, within The MCP Guide. Profiles are checked against each vendor's own documentation. Need a server built? See MCP development.
ServiceNow's MCP support lets AI apps run governed ServiceNow workflows, such as looking up and summarizing incidents and cases. You do not connect to one shared server. Instead, an admin builds MCP servers on your own instance with the MCP Server Console and chooses which tools each one exposes.
Checked against: ServiceNow's MCP Server Console release notes, ServiceNow's MCP Server Console FAQ and the ServiceNow connector page on Claude on 2 November 2026. eSEOspace did not install or test this server.
Key Takeaways
- The MCP Server Console is new in ServiceNow's Zurich release and comes from the ServiceNow Store.
- It becomes available once a Now Assist application is active, and it uses the Model Context Protocol Server plugin (
sn_mcp_server). - Admins build servers from Now Assist skills, knowledge graphs, subflows, actions and scripted REST APIs.
- Clients connect with OAuth 2.0 authorization code grant. Dynamic Client Registration is not supported.
- ServiceNow recommends its AI Gateway in AI Control Tower for audit history and sensitive data protection.
At a glance
| Item | Detail |
|---|---|
| Publisher | ServiceNow |
| Official? | Yes |
| Hosting | Remote, on your ServiceNow instance |
| Transport | Streamable HTTP; no stdio or local servers |
| Sign-in | OAuth 2.0 authorization code grant; third-party IdPs on newer patches |
| Read or write | Depends on the tools you build; scripted REST APIs can read and write |
| Price | Not published; tied to Now Assist licensing |
| Source code | Closed (platform feature) |
| Status | Listed as "Anthropic verified" in Claude's directory |
What it can do
The Claude directory listing says the connector runs "governed workflows and actions across IT, HR, Customer Service, Security, Risk" and other departments. It lists no tools, because "available tools reflect" what your admin provisions.
ServiceNow's release notes and FAQ describe these tool sources:
| Tool source | Notes |
|---|---|
| Now Assist skills | Choose which fields become tool inputs |
| Knowledge graph | Graph queries, with access control at each node |
| Subflows | Synchronous only |
| Actions | Synchronous only |
| Scripted REST APIs | GET, POST and PUT; read and write |
A preconfigured Quickstart Server looks up and summarizes incident and case records. The FAQ says its tools depend on which Now Assist store apps you have; for example, Now Assist for ITSM enables the incident tools.
You can build separate servers for separate jobs, such as one for HR and one for IT, and choose which fields become tool inputs. The release notes also mention tool annotations and MCP Apps for interactive tool screens.
How to connect it
- Activate a Now Assist application and install the MCP Server Console from the ServiceNow Store. Check the Store listing for patch compatibility.
- Create a server in the console and add tools.
- Register an OAuth client. The console's server wizard can do this, or you can use Machine Identity Console under Inbound integrations with "OAuth - Authorization code grant" and JWT tokens. The FAQ lists
oauth_admin,mi_adminoradminas the roles needed. - Add the server in your AI client and sign in.
In Claude, the ServiceNow connector is on the Connectors page (now Customize > Connectors). The FAQ also names Microsoft Copilot and Moveworks as clients. ServiceNow sends readers to its product docs for server URL formats, so copy the URL from your console. Because DCR is not supported, every client must be registered by hand. The FAQ says Client ID Metadata Documents (CIMD) work from Australia Patch 1 or Zurich Patch 7. See Dynamic Client Registration explained.
Security notes
The Claude listing says the connector respects existing ServiceNow permissions and security controls. Still, a tool built on a scripted REST API with POST or PUT can change records, so give write tools their own server and narrow roles.
The FAQ says audit history comes from AI Control Tower with AI Gateway, which traces each tool call to its agent, client and server and can block data such as social security and credit card numbers. Without AI Gateway, the FAQ says there is no automated data interception in the MCP traffic path. See MCP audit logging.
The OAuth client credentials grant is not supported yet, so each connection acts as a real user.
Alternatives
- Atlassian Rovo MCP Server for Jira Service Management teams.
- PagerDuty MCP server for incident response on call.
- Freshdesk MCP server for lighter customer support desks.
Next step
Start with the Quickstart Server's read-only incident and case tools, route traffic through AI Gateway, then add write tools one at a time. Our MCP readiness audit can help plan the rollout.
More in the MCP Guide
Free tools: MCP Server Risk Checklist · Tool Permission Planner
Latest research: State of MCP: October 2026
Frequently asked questions
Is there a public ServiceNow MCP URL?
No single shared URL is documented. Each server lives on your own instance, and ServiceNow's FAQ points to its product docs for URL formats.
Do I need Now Assist?
Yes. ServiceNow's release notes say the MCP Server Console becomes available once a Now Assist application is activated. Quickstart tools also depend on which Now Assist apps you install.
Can I sign in with Okta or Microsoft Entra?
The FAQ says third-party identity providers, including Okta, Microsoft Entra and Ping Identity, work from Australia Patch 3 or Zurich Patch 10. Microsoft Entra needs one patch later.
What does it cost?
ServiceNow does not publish an MCP price. When asked about Now Assist consumption in the FAQ comments, a ServiceNow employee pointed the question to the account team.
