Until now, Atlassian's Model Context Protocol (MCP) let you connect AI assistants and chat platforms to the standard Jira and Confluence environment to manage generic work items or documentation. However, for support and operations (ITSM) teams, a key piece was missing: service-specific context.
With the new Atlassian MCP update, the protocol expands its reach by adding native tools designed exclusively for Jira Service Management (JSM).
In service management, work no longer happens only inside the ITSM console; it starts in Slack, Microsoft Teams or in assistants like Claude. Now, MCP-compatible agents and clients can interact directly with real support and operations workflows without forcing teams to jump between tabs, securely accessing:
- End-to-end request management: Create, triage and resolve support tickets directly from the conversation.
- Real-time alert control: Acknowledge, close and escalate critical incidents before they impact the service or breach an SLA.
- On-call schedules: Check on-call calendars and team availability instantly.
- Asset search (Assets/CMDB): Locate resources, configurations and infrastructure linked to an incident.
- Knowledge base: Draft new help articles from recent resolutions.
Whereas before it was only possible to work with conventional Jira issues, this evolution turns Atlassian MCP into a true operational bridge for JSM, bringing critical context exactly where your team works.
👉 Get all the details here
Content sponsored by Quabu Solutions

