Breaking mcp
On Mar 1, 2027 every v1 Rovo MCP connection starts exposing the v2 tools; v2 is GA now at /v2/mcp
What changes
v2 went GA on Sep 8, 2026 at https://mcp.atlassian.com/v2/mcp with new and improved Jira and Confluence tools and new products (Loom, Goals, Projects, Team, Focus, Talent, Bitbucket). From Mar 1, 2027 existing v1 usage is switched to the v2 tools automatically. Incompatible clients must clear cached client ids or .well-known credentials to keep authenticating. For MCP gateways, https://mcp.atlassian.com/v2/mcp?tools=all exposes a flat tool list, and tools/list returns it paginated at 50 tools per page, so a client that reads only the first page sees a partial set.
Breaking: Calls fail after this date.
What to do
Move to /v2/mcp before the cutoff, diff the tool set with apiwatch probe, and make sure the client paginates tools/list; clear cached clientIds and .well-known credentials if the client can't re-authenticate after the switch.
Strings to search for
mcp.atlassian.com/v1