# /v1/* changes: it serves the v2 tools

Calls to /v1/* on Atlassian MCP stop working on March 1, 2027.

On March 1, 2027, calls to /v1/* will automatically start to expose and utilize v2 tools instead of the previous behavior. Incompatible calls fail after this change takes effect. Clients that are incompatible will need to clear cached clientIds or .well-known credentials to continue using the service.

## What to use instead

Switch to the v2 endpoint at mcp.atlassian.com/v2/mcp and complete authorization again. The move requires more than changing an identifier because v2 is a separate OAuth resource with its own tool names.

- API: Atlassian MCP (mcp.atlassian.com)
- Kind: Behaviour change
- Takes effect: March 1, 2027
- Calls after that day: fail
- Calls it hits: `/v1/*`
- Source: [Announcement](https://support.atlassian.com/atlassian-ai-gateway/docs/how-to-upgrade-from-atlassian-rovo-mcp-v1-to-atlassian-rovo-mcp-v2/)
- Verified: October 29, 2026, against Atlassian MCP's own pages
- Page: https://www.okapi.bot/providers/atlassian-mcp/breaking-changes/v1-changes-it-serves-the-v2-tools/

## Atlassian MCP's words

> On March 1 2027 any existing utilization of v1 will automatically start to expose and utilize v2 tools. Any incompatible clients will need to clear cached clientIds or .well-known credentials to support continued use of Atlassian MCP.

Okapi finds the calls this change hits in your repo and opens the pull request with the fix: https://github.com/apps/okapi-agent