New Jira Service Management tools and Operations tools in the new Atlassian MCP

The Atlassian Rovo MCP Server is adding twelve Jira Service Management tools through MCP V2. These tools support searching and triaging requests, reviewing and approving Request Resolver plans, creating customer requests, transitioning requests, deciding pending approvals, and reading or setting Workforce Management agent availability.

New tool	Description
getJsmRequestResolverPlans	Retrieve Request Resolver plan status, readable steps, and runbook links for selected JSM requests.
searchJsmRequests	Search and triage caller-visible JSM requests using JQL, SLA, sentiment, and resolver-plan signals.
getJsmRequest	Retrieve details and the current customer-facing state of a JSM request.
getJsmRequestActionMetadata	Discover customer-visible transitions and optionally retrieve request-type field or approval metadata before a follow-up action.
getJsmRequestCreationOptions	List the service desk and request types available when preparing to create a JSM customer request.
getJsmRequestTypeFields	Retrieve required fields, field IDs, and allowed values for a selected JSM request type.
getJsmAgentAvailability	Read Workforce Management agent availability for a JSM service project.
approveJsmRequestResolverPlans	Approve reviewed Request Resolver plans for explicitly selected JSM requests.
transitionJsmRequest	Perform a customer/request-portal-visible transition on a JSM request.
createJsmRequest	Create a JSM customer request using an explicit service desk, request type, and request field values.
decideJsmRequestApproval	Approve or decline a pending approval on a JSM request.
setJsmAgentAvailability	Set an agent's Workforce Management availability to available or on break for a JSM service project.

The four existing Operations tools getJsmOpsAlerts, getJsmOpsScheduleInfo, getJsmOpsTeamInfo, and updateJsmOpsAlertare also moving from MCP V1 to MCP V2. They retain their existing names and are not counted as new tools.

JSM tools in MCP V2 support OAuth 2.1 and API token authentication. Read tools belong to read_jsm and require read:jsm:agent-interface; write tools belong to write_jsm and require write:jsm:agent-interface. getJsmRequestResolverPlans, searchJsmRequests, and approveJsmRequestResolverPlans also require read_jira and read:jira:agent-interface. updateJsmOpsAlert additionally requires read:jsm:agent-interface.

Tool availability depends on granted scopes, the permission groups enabled by your organization admin, and your app access. See Supported tools for details.