ITSM MCP Server release notes
The ServiceNow® ITSM MCP Server application connects an AI-enabled Model Context Protocol (MCP) client application to your ServiceNow environment using the ITSM MCP Server. This connection enables incident and change management for service desk agents and IT managers, and enables requesters to check and manage their own tickets.
About ITSM MCP Server
-
Incident management: Retrieve, modify, and search incidents; answer natural-language questions about incident data.
-
Change management: Execute end-to-end change lifecycle with approvals, risk evaluation, and quality assurance across multiple tables.
-
Request management: Create incidents with knowledge deflection, check status, escalate, and add customer-visible comments.
-
On-call scheduling: Retrieve rosters and shifts, request time off, and query availability through natural-language questions.
See ITSM MCP Server for more information.
Activation and other requirements
- Activation information
- Activate these plugins to use ITSM MCP Server:
- Now Assist for ITSM plugin (sn_itsm_gen_ai)
- Model Context Protocol Server (sn_mcp_server)
- ITSM MCP Server (sn_itsm_mcp_server)
Australia Patch 7 and Version 3.3
Some of the ITSM MCP tools have been renamed and have also been made available to fulfillers and requesters in ITSM MCP Server in this release.
What's changed
- Changes to the ITSM MCP Server tools
-
- You need the sn_mcp_server.viewer role as the base role to access ITSM MCP server.
- The sn_itsm_mcp_server.incident.get_details and sn_itsm_mcp_server.incident.modify incident tools are available to both fulfillers and requesters.
- As a fulfiller, you can use the sn_itsm_mcp_server.incident.modify tool to also escalate incidents.
- As a requester, you can use the sn_itsm_mcp_server.incident.get_details to check the status of a specific incident.
- The sn_itsm_mcp_server.requester.add_comment tool has been renamed to sn_itsm_mcp_server.request.modify.
- As a requester, you can use the sn_itsm_mcp_server.request.modify tool to add customer-visible comments to the requested items.
- As a fulfiller, you can use the sn_itsm_mcp_server.incident.modify to add customer-visible comments to incidents.
What's deprecated or removed
- Deprecated sn_itsm_mcp_server.requester.escalate tool
- The sn_itsm_mcp_server.requester.escalate tool is turned off by default. Use sn_itsm_mcp_server.incident.modify with the escalate and escalation_reason inputs instead.
Australia Patch 4 and Version 3.2
Manage incidents, change requests, request items, and on-call schedules with the ITSM MCP Server. Empower requesters to handle their own tickets and access shared tools for approvals and ITSM data queries.
What's new
- Managing incidents
- Use incident management tools to get details, update fields, and find similar incidents in the ITSM MCP Server.
For example:
- Get incident fields including state, priority, assignment, CI, description, and work notes with
incident.get_details. - Update incident fields and work notes through platform-native APIs with full business rule execution using
incident.modify. - Search for similar incidents using semantic search with
incident.search_similar, and look up assignment groups and users withlookup_assignment_groupsandlookup_users. - Search similar Knowledge Base (KB) articles using
incident.search_similar_kb, and retrieve details for a published KB article usingincident.get_kb_details. - Link a KB article to an incident as a related reference using
incident.attach_kb.
- Get incident fields including state, priority, assignment, CI, description, and work notes with
- Managing change requests
- Use change management tools to query, analyze, and update change requests in the ITSM MCP Server.
For example:
- Create and update change requests, calculate risk, and manage planned outages with
change.lifecycle. - Analyze changes by recommending assignment groups, retrieving risk and impact data, and suggesting configuration items and templates with
change.analyze. - Retrieve, search, and aggregate change data, check schedules and conflicts, and score data quality with
change.query. - List tasks, affected CIs, approvals, incidents, problems, outages, and change policies with
change.relation.
- Create and update change requests, calculate risk, and manage planned outages with
- Managing request items
- Use request item tools to create and manage your own tickets in the ITSM MCP Server.
For example:
- Create incidents or request catalog items through a guided workflow that includes knowledge base deflection, catalog item redirection, and duplicate detection using
requester.create_incident. - Escalate an incident's urgency with a mandatory reason using
requester.escalate. - Add customer-visible comments to your open incidents or requested items using
requester.add_comment.
- Create incidents or request catalog items through a guided workflow that includes knowledge base deflection, catalog item redirection, and duplicate detection using
- Managing on-call schedules
- Use on-call management tools to look up coverage and manage your on-call schedule in the ITSM MCP Server.
For example:
- Identify current on-call engineers by assignment group or shift name, and view your next or active on-call shift details using
oncall.on_call_lookup. - Request time off from an on-call shift and arrange coverage through a two-phase analyze-and-create workflow using
oncall.timeoff_request.
- Identify current on-call engineers by assignment group or shift name, and view your next or active on-call shift details using
- Using ITSM MCP Server common tools
- Use common tools to use with the ITSM MCP Server.
For example:
- Answer structured natural language questions about ITSM data, including details on incidents, change requests, and active catalog items using
itsm_knowledge_graph. - Approve or reject your oldest pending approval for a change or request items using
task_approval_decision. - Get the authenticated user's current session time zone and the current date and time in that time zone using
get_session_timezone.
- Answer structured natural language questions about ITSM data, including details on incidents, change requests, and active catalog items using