This page includes release notes and updates for Atlassian Rovo MCP for developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from the Atlassian Rovo MCP team.
Go to our Atlassian Rovo MCP community to ask questions.
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.
Rate this page: