Atlassian MCP
/v1/* changes: it serves the v2 tools
Stops workingSubscribe to Atlassian MCPShare
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.
Calls it hits
/v1/*
What to use instead of these calls
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.
In 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.
Facts
- API
- Atlassian MCP
mcp.atlassian.com - Kind
- Behaviour change
- Takes effect
- March 1, 2027
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Atlassian MCP's own pages
Questions
When does this change take effect?
Calls to /v1/* on Atlassian MCP stop working on March 1, 2027.
What happens to calls after March 1, 2027?
They fail from that day.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Atlassian MCP 1
-
MCP tool findJiraIssueAssignableUsersTool removal Stopped working
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix before March 1, 2027.