--- sourceDocument: australia Combined Product Files sourceDocumentLink: https://www.servicenow.com/docs/r/australia/delta-zurich-australia Release : - australia ft:locale : - en-US ft:publication_title : - australia Combined Product Files ft:clusterId : - delta3az bundleId : - delta3az --- # Combined ITSM MCP Server release notes for upgrades from Zurich to Australia # Combined ITSM MCP Server release notes for upgrades from Zurich to Australia {#ariaid-title1} Release version: Australia Updated October 8, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Combined ITSM MCP Server Release Notes for Upgrades from Zurich to Australia This consolidated release note guide assists ServiceNow customers in preparing for upgrading the ITSM MCP Server from the Zurich release to the Australia release. It summarizes key features, changes, deprecations, and activation requirements across these releases, enabling customers to understand new capabilities, necessary upgrade tasks, and evolving toolsets within the ITSM MCP Server environment. Show full answer Show less ## Key Features Between Zurich and Australia releases, the ITSM MCP Server provides comprehensive tools for managing incidents, change requests, request items, and on-call schedules, along with common utility tools. These features enable customers to streamline IT service management processes effectively: * **Incident Management:** Retrieve detailed incident data (state, priority, assignment, CI, description, work notes), update incidents via platform-native APIs with full business rule execution, perform semantic searches for similar incidents and knowledge base articles, and link KB articles as references. * **Change Management:** Create, update, and analyze change requests including risk calculation and planned outage management. Query and aggregate change data, check schedules and conflicts, and list related tasks, approvals, and policies. * **Request Item Management:** Create incidents or catalog requests using guided workflows with knowledge base deflection and duplicate detection, escalate incident urgency with mandatory reasons, and add customer-visible comments to open requests. * **On-Call Scheduling:** Lookup current on-call coverage by assignment group or shift, view active or upcoming shifts, request time off, and arrange coverage through a structured analyze-and-create workflow. * **Common Tools:** Respond to structured natural language queries about ITSM data, approve or reject pending approvals, and retrieve session time zone and current date/time information. ## Changes From Zurich to Australia, key changes include: * Base access requires the `snmcpserver.viewer` role for ITSM MCP Server interaction. * Incident tools `incident.getdetails` and `incident.modify` are accessible to both fulfillers and requesters. Fulfillers can escalate incidents using `incident.modify`, while requesters can check incident status using `incident.getdetails`. * The tool formerly known as `requester.addcomment` has been renamed to `request.modify`. Requesters use it to add customer-visible comments to requested items, and fulfillers use `incident.modify` for adding comments to incidents. ## Deprecations The `snitsmmcpserver.requester.escalate` tool is deprecated and turned off by default in both Zurich and Australia releases. Customers should instead use the `incident.modify` tool with the `escalate` and `escalationreason` inputs to escalate incidents, ensuring consistency and leveraging updated APIs. ## Activation Requirements To activate ITSM MCP Server features, customers must enable the following plugins: * Now Assist for ITSM (`snitsmgenai`) * Model Context Protocol Server (`snmcpserver`) * ITSM MCP Server (`snitsmmcpserver`) These activations remain consistent from Zurich through Australia releases to ensure full functionality. ## Practical Implications for ServiceNow Customers Upgrading to Australia provides customers with enhanced and consistent ITSM MCP Server tools to manage incidents, changes, requests, and on-call schedules more effectively. Customers benefit from streamlined workflows, improved incident escalation processes, and natural language query capabilities for faster data insights. Understanding role requirements and updated tool names ensures smooth API transitions. Following activation steps and reviewing pre- and post-upgrade tasks ensures a successful upgrade with minimal disruption. Consolidated page of all release notes for ITSM MCP Server from Zurich to Australia. ## How to use this page To help you prepare for your upgrade, we have combined the cross-family ITSM MCP Server release notes onto one page. Read this summary of the new features, changes, and updated information for your product from Zurich to Australia. Tip: If there were no updates for a release notes section in a certain family release, we included a short note for your reference. For example, if a product did not have any updates in Tokyo, the row says "No updates for this release." ## Important information for upgrading ITSM MCP Server to Australia Before you upgrade to Australia, review these pre- and post-upgrade tasks and complete the tasks as needed. {#dfrn3-itsmmcpserver-summary__entry__2} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## New features Between your current release family and Australia, new features were introduced for ITSM MCP Server. {#dfrn3-itsmmcpserver-summary__entry__8} | Release | Release notes | |-|-| | Zurich | [Managing incidents](https://www.servicenow.com/docs/access?context=manage-incidents-itsm-mcp-server&family=zurich&ft:locale=en-US) : 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 with `lookup_assignment_groups` and `lookup_users`. * Search similar Knowledge Base (KB) articles using `incident.search_similar_kb`, and retrieve details for a published KB article using `incident.get_kb_details`. * Link a KB article to an incident as a related reference using `incident.attach_kb`. [Managing change requests](https://www.servicenow.com/docs/access?context=manage-change-requests-itsm-mcp-server&family=zurich&ft:locale=en-US) : 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`. [Managing request items](https://www.servicenow.com/docs/access?context=manage-employee-experience-itsm-mcp-server&family=zurich&ft:locale=en-US) : 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`. [Managing on-call schedules](https://www.servicenow.com/docs/access?context=manage-on-call-schedule-itsm-mcp-server&family=zurich&ft:locale=en-US) : 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`. [Using ITSM MCP Server common tools](https://www.servicenow.com/docs/access?context=itsm-mcp-server-tools-reference&family=zurich&ft:locale=en-US) : 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`. | | Australia | [Managing incidents](https://www.servicenow.com/docs/access?context=manage-incidents-itsm-mcp-server&family=australia&ft:locale=en-US) : 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 with `lookup_assignment_groups` and `lookup_users`. * Search similar Knowledge Base (KB) articles using `incident.search_similar_kb`, and retrieve details for a published KB article using `incident.get_kb_details`. * Link a KB article to an incident as a related reference using `incident.attach_kb`. [Managing change requests](https://www.servicenow.com/docs/access?context=manage-change-requests-itsm-mcp-server&family=australia&ft:locale=en-US) : 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`. [Managing request items](https://www.servicenow.com/docs/access?context=manage-employee-experience-itsm-mcp-server&family=australia&ft:locale=en-US) : 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`. [Managing on-call schedules](https://www.servicenow.com/docs/access?context=manage-on-call-schedule-itsm-mcp-server&family=australia&ft:locale=en-US) : 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`. [Using ITSM MCP Server common tools](https://www.servicenow.com/docs/access?context=itsm-mcp-server-tools-reference&family=australia&ft:locale=en-US) : 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`. | [ ] ## Changes Between your current release family and Australia, some changes were made to existing ITSM MCP Server features. {#dfrn3-itsmmcpserver-summary__entry__14} | Release | Release notes | |-|-| | Zurich | [Changes to the ITSM MCP Server tools](https://www.servicenow.com/docs/access?context=itsm-mcp-server-tools-reference&family=zurich&ft:locale=en-US) : * 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. | | Australia | [Changes to the ITSM MCP Server tools](https://www.servicenow.com/docs/access?context=itsm-mcp-server-tools-reference&family=australia&ft:locale=en-US) : * 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. | [ ] ## Removed Between your current release family and Australia, some ITSM MCP Server features or functionality were removed. {#dfrn3-itsmmcpserver-summary__entry__20} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Deprecations Between your current release family and Australia, some ITSM MCP Server features or functionality were deprecated. {#dfrn3-itsmmcpserver-summary__entry__26} | Release | Release notes | |-|-| | Zurich | [Deprecated sn_itsm_mcp_server.requester.escalate tool](https://www.servicenow.com/docs/access?context=manage-employee-experience-itsm-mcp-server&family=zurich&ft:locale=en-US) : 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 | [Deprecated sn_itsm_mcp_server.requester.escalate tool](https://www.servicenow.com/docs/access?context=manage-employee-experience-itsm-mcp-server&family=australia&ft:locale=en-US) : 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. | [ ] ## Activation information Review information on how to activate ITSM MCP Server. {#dfrn3-itsmmcpserver-summary__entry__32} | Release | Release notes | |-|-| | Zurich | 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) For details, see [Activate the ITSM MCP Server](https://www.servicenow.com/docs/access?context=set-up-itsm-mcp-server&family=zurich&ft:locale=en-US). | | Australia | 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) For details, see [Activate the ITSM MCP Server](https://www.servicenow.com/docs/access?context=set-up-itsm-mcp-server&family=australia&ft:locale=en-US). | [ ] ## Additional requirements If any additional requirements were introduced or changed for ITSM MCP Server we have noted them here. {#dfrn3-itsmmcpserver-summary__entry__38} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Browser requirements If any specific browser requirements were introduced or changed for ITSM MCP Server we have noted them here. {#dfrn3-itsmmcpserver-summary__entry__44} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Accessibility information Review details on accessibility information for ITSM MCP Server, such as specific requirements or compliance levels. {#dfrn3-itsmmcpserver-summary__entry__50} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Localization information If there are specific localization considerations for ITSM MCP Server we have noted them here. {#dfrn3-itsmmcpserver-summary__entry__56} | Release | Release notes | |-|-| | Zurich | No updates for this release. | | Australia | No updates for this release. | [ ] ## Highlight information If there are specific highlight considerations for ITSM MCP Server we have noted them here. {#dfrn3-itsmmcpserver-summary__entry__62} | Release | Release notes | |-|-| | Zurich | Using ITSM MCP Server, manage incidents, change requests, and on-call schedule. You can also check the status of your own incidents and requested items, and escalate incidents. * 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](https://www.servicenow.com/docs/access?context=itsm-mcp-server-overview&family=zurich&ft:locale=en-US) for more information. | | Australia | Using ITSM MCP Server, manage incidents, change requests, and on-call schedule. You can also check the status of your own incidents and requested items, and escalate incidents. * 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](https://www.servicenow.com/docs/access?context=itsm-mcp-server-overview&family=australia&ft:locale=en-US) for more information. | [ ]