ST-2026-245 · APIs & integration
Atlassian makes Rovo MCP v2 generally available
Atlassian made Rovo MCP v2 generally available at its v2 endpoint and scheduled existing v1 utilisation to expose and use v2 tools from 1 March 2027.
Previous state
Rovo MCP v2 had been in Preview since 1 July 2026 at its preview endpoint, while existing third-party client and plugin integrations could continue to use the v1 tool surface.
Current state
Rovo MCP v2 is generally available at https://mcp.atlassian.com/v2/mcp; Atlassian is updating existing integrations, and from 1 March 2027 existing v1 utilisation automatically exposes and uses v2 tools.
Affected users
Who needs to care
Rovo MCP users, administrators, third-party MCP clients and plugin integrations using either the v2 endpoint or the existing v1 tool surface.
Required response
What to do
Adopt the v2 endpoint for new integrations, verify client compatibility and update existing integrations before the stated v1 tool-surface transition; affected clients may need cached tool identifiers or .well-known credentials cleared.
Evidence boundary
What the source does not prove
Atlassian proves v2 general availability, the v2 endpoint and the bounded 1 March 2027 v1-to-v2 tool behaviour. It does not prove that every client is incompatible, that the v1 endpoint disappears, or that Preview and GA are separate event families.
Lifecycle history
Dated event sequence
- Rovo MCP v2 Preview began
Atlassian introduced the v2 tool surface in Preview.
- Rovo MCP v2 generally available
Atlassian made the v2 endpoint generally available and described integration updates.
- Existing v1 utilisation transitions to v2 tools
Atlassian says existing v1 utilisation will automatically expose and use the v2 tool set.
Evidence ledger
First-party sources
- 01Atlassian Developer — Rovo MCP changelog — v2 general availability
Official Atlassian Rovo MCP lifecycle and transition authority · 2026-09-08
Open official source ↗