Atlassian MCP now supports Claude-issued Managed Auth, enabling Enterprise-managed authentication (EMA) / Cross App Access (XAA) directly from Claude without a dependency on an additional IdP.

For more details on how to get started, please review the Configure enterprise-managed authentication guide.

The Atlassian Rovo MCP Server is adding six new Jira Align tools through MCP V2 across two new toolsets: read_jira_align and write_jira_align. These tools enable AI agents and workflows to interact directly with Jira Align data for portfolio reporting, planning rollups, terminology discovery, and backlog hygiene.

Jira Align tools in MCP V2 support OAuth 2.1:

• Read tools belong to the read_jira_align toolset and require the read:jira-align:agent-interface scope.

• Write tools belong to the write_jira_align toolset and require the write:jira-align:agent-interface scope.

• Admin enablement: Organization Admins must enable the Jira Align toolsets in Admin Hub under Security > Data protection > Atlassian Rovo MCP server (or MCP tool settings) before users can access them.

• Re-authorization: Users will need to re-authorize or reconnect their MCP client to grant the new Jira Align scopes.

• Requirements: Requires Jira Align Cloud, Atlassian Guard enabled, an active Jira Align Bridge mapping connecting the sites, and the user to have logged in to the Jira Align UI at least once.

Tool availability depends on granted scopes, the permission groups enabled by your organization admin, and your app access. For details on these tools, please refer to our https://developer.atlassian.com/cloud/rovo-mcp/guides/supported-tools/ documentation.

We’re excited to announce that the below Confluence suggested edits tools have been added to Confluence on Atlassian MCP. Users who have previously approved access to the respective toolsets will start to see availability of these tools shortly as the feature is progressively rolled out.

write_confluence:

• addConfluenceContentSuggestions

read_confluence:

• getConfluenceContentSuggestions

For details on this tool and other tools available on Atlassian MCP, please refer to our Supported Tools.

The tool listJiraIssueComments as part of the read_jira toolset has been updated.

It is now a primary tool: it is returned directly in the MCP tools/list response and can be called by name, alongside getJiraIssue, searchJiraIssuesUsingJql, createJiraIssue, editJiraIssue, transitionJiraIssue and addOrEditJiraIssueComment. Previously it was a deferred tool, reachable only through discover followed by executeRead. It no longer appears in discover results; discover lists it under primaryTools instead, and calling it through executeRead continues to work.

Inputs, outputs, toolset and the read:jira:agent-interface scope are unchanged.

As of October 16, 2026, the following legacy Loom MCP tools are no longer returned to users in the Loom V2 rollout cohort.

Use these replacement tools:

• listLoomVideos and listLoomVideosSharedWithMe → listLoomObjects

• getLoomVideo → getLoomObjectsContent

• getLoomVideoComments and getLoomMeetingActionItems → getLoomObjectsContent with the applicable content expansion

• createLoomVideoComment and createLoomVideoReaction → addLoomInteraction

• updateLoomVideoTitle → updateLoomObjectMetadata

• updateLoomVideoPermissions → updateLoomObjectVisibility=

• shareLoomVideo → shareLoomObject

• createLoomVideoUpload → createLoomObjectUpload

• publishLoomVideo → publishLoomObject

• listLoomFolders → listLoomObjectFolders

• createLoomFolder → createLoomObjectFolder

• moveLoomVideoToFolder → moveLoomObjectToFolder

Compatibility for getLoomVideo

getLoomVideo is unlisted rather than immediately disabled. New tool-list responses do not advertise it, but existing sessions that cached its schema can continue calling it during the compatibility period. New integrations should use getLoomObjectsContent.

Tools that remain available

getLoomVideoDownloadUrl and recoverLoomVideo are not replaced by this migration.

This is the removal half of the coordinated Loom MCP V2 migration announced in CHANGE-3503.

Atlassian Rovo MCP is migrating Loom recording workflows to a consolidated V2 Loom Object tool surface.

Loom objects currently include async videos and meeting recordings. The new tools use consistent object-based names so that Loom can support more content types without another tool migration.

For each rollout cohort, the V2 tools replace the corresponding V1 tools. The MCP server will advertise only the applicable V2 replacement operations.

The V2 tools support:

• Loom ARIs, share URLs, and embed URLs as recording identifiers.

• Async videos and meeting recordings through the same tool contracts.

• Consolidated comments and reactions.

• Batch retrieval with one result per requested recording.

• Explicit recording and content-component statuses.

• Transcript, agent brief, action item, comment, attached-link, and developer-log retrieval.

• Consistent folder operations for Loom objects.

• listLoomObjects replaces listLoomVideos and listLoomVideosSharedWithMe.

• getLoomObjectsContent replaces getLoomVideo for supported metadata, transcripts, agent briefs, action items, comments, attached links, and developer context logs.

• addLoomInteraction replaces createLoomVideoComment and createLoomVideoReaction.

• updateLoomObjectMetadata replaces updateLoomVideoTitle and also supports description updates.

• updateLoomObjectVisibility replaces updateLoomVideoPermissions.

• shareLoomObject replaces shareLoomVideo.

• createLoomObjectUpload replaces createLoomVideoUpload.

• publishLoomObject replaces publishLoomVideo.

• listLoomObjectFolders replaces listLoomFolders.

• createLoomObjectFolder replaces createLoomFolder.

• moveLoomObjectToFolder replaces moveLoomVideoToFolder.

The tools remain in the existing read_loom and write_loom permission groups. This migration does not add a new organization-admin permission.

The following operations are not replaced by this migration:

• getLoomVideoDownloadUrl

• recoverLoomVideo

Availability will move through rollout cohorts. Users outside the V2 cohort will continue to receive the V1 tool surface until their cohort moves to V2.

getLoomVideo is a high-frequency tool whose schema may be cached by MCP clients. During its deprecation period, the server will stop advertising it in tools/list and discover. However, an existing client with the cached tool can continue to call it by its exact name. This prevents active sessions from failing while new and refreshed sessions move to getLoomObjectsContent.

The other replaced V1 operations use the discover and execute flow. They will be removed from the enabled operation list for each V2 cohort.

The team will monitor calls to the unlisted getLoomVideo operation. A later cleanup change will remove the old operation and its supporting action after cached usage reaches an agreed safe level.

For details about these tools and other tools available in the Atlassian Rovo MCP Server, see the supported-tools documentation.

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.

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.

What's changing
From January 1, 2027, Atlassian cloud will add new IP address ranges as we expand our cloud infrastructure.

The new ranges are in addition to our existing ones.

The new ranges are:

• New range: 131.162.88.0/21

  • Requests to Atlassian (browsers and your clients calling Atlassian APIs): 131.162.88.0/23

  • Requests from Atlassian (webhooks, Connect lifecycle calls, and other requests from Atlassian to your app): 131.162.90.0/23

What you need to do
If your app, remote backend, or integration allowlists Atlassian IP addresses, you must add these ranges before January 1, 2027, to avoid service interruptions.

These ranges are already included in our official IP range list (viewer tool). If you automate your allowlist updates from this file, no further action is required. For more details, see our documentation on IP addresses and domains for Atlassian cloud apps.

We’re excited to announce that the below tools now support showing rich UI cards on Atlassian MCP V2.

• Jira : getJiraIssue, editJiraIssue, createJiraIssue, transitionJiraIssue, and searchJiraIssuesUsingJql

• Confluence : searchConfluence

NOTE: We are doing a steady rollout across all customers, and if you do not see these by Oct 23, 2026 , please reach out to support.

We’re excited to announce that getJiraScreen and updateJiraScreen have been added to manage_jira on Atlassian MCP. Users who have previously approved access to manage_jira will start to see availability of these tools shortly.

For details on these tools and other tools available on Atlassian MCP, please refer to our Supported Tools.

We’re excited to announce that organization admins can now set up the Atlassian Rovo MCP server control in Data Security Policy. Admins can govern how external AI tools read and write Jira and Confluence data using MCP, with org-wide defaults and overrides scoped by Atlassian apps, spaces, and classification levels. It works the same way as existing DSP controls like data export, anonymous access, and public links.

To get started:

1. Go to Atlassian Administration. Select your organization if you have more than one.

2. Select Security.

3. Select Data protection, then select Data security policies.

4. Edit the Atlassian Rovo MCP server control.

For more details read our documentation.

We’re excited to announce that the below Confluence Remix tools have been added to Confluence on Atlassian MCP. Users who have previously approved access to the respective toolsets will start to see availability of this tool shortly.

write_confluence:

• createConfluenceInfographicForPage

• editConfluenceInfographicForPage

• createConfluenceMauiApp

• editConfluenceMauiApp

read_confluence:

• getConfluenceMauiApp

For details on this tool and other tools available on Atlassian MCP, please refer to our Supported Tools.

🛠️ Scheduled maintenance window from September 25 @ 5PM PST to Monday, September 28 @ 10AM, AEST

Our support portal is moving to a new home. New ticket submissions and ticket access including comments via email will be unavailable during this window. Starting September 28, submit all requests at Atlassian Support and update your bookmarks. Learn what's changing.

We’re excited to announce that getJiraWorkflowEditorLink has been added to manage_jira on Atlassian MCP. Users who have previously approved access to manage_jira will start to see availability of this tool shortly.

For details on this tool and other tools available on Atlassian MCP, please refer to our Supported Tools.

We’re excited to announce that getJiraWorkflows has been added to manage_jira on Atlassian MCP. Users who have previously approved access to manage_jira will start to see availability of this tool shortly.

For details on this tool and other tools available on Atlassian MCP, please refer to our Supported Tools.