- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
MCP-compatible AI clients are becoming a new way to start enterprise work. But turning a prompt into a governed business outcome still requires purpose-built tools.
That is why ServiceNow is launching out-of-the-box MCP Servers for ITSM, ITOM, CMDB, and SPM. They let supported clients such as Claude, Copilot, and Gemini call ServiceNow tools without every customer rebuilding the same domain logic.
Not another API wrapper
Our MCP tools are optimized around outcomes. They reduce the read-query-reason-retry loop that happens when an AI client works directly against generic table access.
|
Better outcomes
Purpose-built tools return more relevant context and apply domain logic to help the AI client produce more accurate results.
|
Fewer tokens
The tool returns focused context for the job instead of broad table results.
|
Fewer calls, faster results
Domain logic runs within the tool, reducing back-and-forth between the AI client, APIs, and data.
|
Change Management example: In our July 11-prompt benchmark, the MCP path produced approximately 52% lower Claude-side cost, 72% faster execution, and about 6.5 times fewer output tokens than direct Table API access.
Simple CRUD does not always show the same advantage. Complex, workflow-heavy work does.
Governance stays on the Now Platform
The AI client decides which tool to call. ServiceNow controls what that tool can see and do. Every request runs in the user’s context and through the same hardened platform controls customers have already modeled, built, and rely on today, allowing them to extend their existing ServiceNow investments into agentic workflows. We are also adding further governance and resilience for this new way of working.
|
ACL and role enforcement
Table and record access follows the authenticated user’s permissions. MCP does not bypass ServiceNow ACLs.
|
Server-side orchestration
Domain logic, workflow steps, validations, and supported actions execute on ServiceNow instead of being reconstructed by the model.
|
Governed action
Actions stay within the ServiceNow workflow layer, with platform visibility and controls around execution.
|
Built around the jobs customers asked us to solve
|
Incident and change work
Pull related records, find similar incidents, assess change risk and conflicts, and update the record through the same conversation.
|
Alerts to service impact
Analyze an alert, surface related incidents and affected services, and identify the next operational step.
|
|
CMDB search with context
Find CIs and services, follow their relationships, and understand topology or blast radius without stitching together raw table results.
|
Portfolio status
Review goals, portfolio plans, projects, milestones, and delivery health from the AI client teams already use.
|
What customers are telling us
“There’s goodness in the out-of-the-box tools that you have.”Customer evaluating the ITSM MCP Server through an enterprise MCP gateway
“Finding CIs means we catch scheduling conflicts before we schedule the change.”Customer feedback on using CMDB and Change Management tools
Generally available September 10, 2026
The ITSM, ITOM, CMDB, and SPM MCP Servers are available for supported MCP clients.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
