🛠️ 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.

We’re excited to announce that createJiraIssueRemoteIssueLink has been added to write_jira on Atlassian MCP. Users who have previously approved access to write_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 convertJiraIssueHierarchy has been added to write_jira on Atlassian MCP. Users who have previously approved access to write_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.

The tool editJiraIssue as part of the write_jira toolset has been updated.

Three optional input fields have been added: rankBeforeIssue, rankAfterIssue and rankCustomFieldId. They rank the work item directly above or below another work item on a board or backlog. rankCustomFieldId selects the rank field when a board uses a custom one.

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

An optional input field reactionDetail has been added, with the values none, summary and users. none (the default) returns comments only. summary adds emoji reaction counts and whether the current user reacted. users also names who reacted.

The tools searchJiraIssuesUsingJql as part of the search_jira toolset and getJiraBoardIssueData as part of the read_jira toolset have been updated.

The optional input field validation has been removed from both tools. Requests that still include it continue to work; the field is ignored.

What’s changing

We’ve introduced new tools for individual capacity planning in the Atlassian Model Context Protocol (MCP). These tools allow you to interact with capacity plans directly through AI-powered interfaces using the read_capacity_planning and write_capacity_planning toolsets.

The new toolsets include 5 tools that enable you to:

• View individual team member allocations.

• Manage work allocations across projects and work items.

What you need to do

If your organization uses auto-enablement for toolset groups, these tools may not be immediately available to all users. Admins can manage access and enable these toolsets through the Atlassian MCP section in the Admin portal.

For more information on how to use these tools, see the supported tools documentation.

The tool findJiraIssueAssignableUsers as part of read_jira toolset has been updated.

The tool has now been renamed to listJiraIssueAssignableUsers

We’re excited to share that a new version of Atlassian Rovo MCP is now available. This release introduces some significant changes including:

• Support for new products - Loom, Goals, Projects, Team, Focus, Talent and Bitbucket.

• New and improved Jira and Confluence tools, introducing support for attachments, whiteboards, databases, sprints and more.

More details about new and available tools are available here.

The new Atlassian Rovo MCP endpoint is now available at https://mcp.atlassian.com/v2/mcp and can be utilised today. Existing plugins and connectors on third-party platforms are being updated and may require you to re-add the plugin/connector for some clients.

We’re excited to share that a preview release of our new Atlassian Rovo MCP is now available for early access. This release introduces some significant changes including:

• Dozens of new tools abstracted behind discover and execute tools

• New and improved Confluence tools, introducing support for attachments, whiteboards, databases and more.

• Reduced default tool exposure, reducing context window consumption by >50%

• Optimised tool responses, substantially reducing context window consumption from tool invocations

The preview endpoint is now available at https://mcp.atlassian.com/v1/mcp/preview and can be utilised today.

Atlassian Rovo MCP will start utilising a different auth server (Atlassian Identity) for DCR OAuth from May 27, 2026. Any existing client implementations must ensure that they are not caching the auth state (including client_id and the /.well-known/oauth-authorization-server discovery document) as these will not be recognised the by the new server.

The new DCR OAuth implementation can be tested in the interim through the use of the https://mcp.atlassian.com/v1/mcp/authv2 url. In addition, this the new authorisation server details can be temporarily obtained via https://mcp.atlassian.com/.well-known/oauth-protected-resource/v1/mcp/authv2.

From May 27, 2026 all requests to https://mcp.atlassian.com/v1/mcp/ will utilise the new auth server and any clients which are still caching may start to fail.