{"slug":"atlassian-mcp","name":"Atlassian MCP","host":"mcp.atlassian.com","site":"https://atlassian.com","category":"productivity","docsUrl":null,"sources":[{"kind":"changelog","url":"https://developer.atlassian.com/cloud/rovo-mcp/changelog/"},{"kind":"archive","url":"https://support.atlassian.com/atlassian-ai-gateway/docs/how-to-upgrade-from-atlassian-rovo-mcp-v1-to-atlassian-rovo-mcp-v2/"}],"url":"https://www.okapi.bot/providers/atlassian-mcp/","json":"https://www.okapi.bot/api/v1/providers/atlassian-mcp.json","breakingChanges":[{"slug":"v1-changes-it-serves-the-v2-tools","api":"atlassian-mcp","title":"/v1/* changes: it serves the v2 tools","kind":"behaviour_change","outcome":"fails","model":null,"announcedAt":null,"effectiveAt":"2027-03-01","scope":null,"calls":["/v1/*"],"method":null,"path":"/v1/*","source":{"url":"https://support.atlassian.com/atlassian-ai-gateway/docs/how-to-upgrade-from-atlassian-rovo-mcp-v1-to-atlassian-rovo-mcp-v2/","kind":"archive"},"quote":"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.","migration":"Move to https://mcp.atlassian.com/v2/mcp and authorize again: v2 is a separate OAuth resource, with its own tool names.","migrationChange":null,"needsDecision":null,"text":{"summary":"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.","migration":"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.","by":"writer"},"publishedAt":"2026-10-28T14:11:15.642Z","updatedAt":"2026-10-28T16:17:20.221Z","status":"upcoming","tone":"risk","url":"https://www.okapi.bot/providers/atlassian-mcp/breaking-changes/v1-changes-it-serves-the-v2-tools/"},{"slug":"the-findjiraissueassignableusers-tool-stops-working","api":"atlassian-mcp","title":"The findJiraIssueAssignableUsers tool stops working","kind":"removal","outcome":"fails","model":null,"announcedAt":null,"effectiveAt":"2026-09-22","scope":null,"calls":["MCP tool findJiraIssueAssignableUsers"],"method":null,"path":null,"source":{"url":"https://developer.atlassian.com/cloud/rovo-mcp/changelog/","kind":"archive"},"quote":"The tool has now been renamed to listJiraIssueAssignableUsers","migration":"Call listJiraIssueAssignableUsers: the tool was renamed.","migrationChange":null,"needsDecision":null,"text":{"summary":"On September 22, 2026, the tool findJiraIssueAssignableUsers will be removed. Calls to MCP tool findJiraIssueAssignableUsers will fail after that date.","migration":"Call listJiraIssueAssignableUsers instead, as the tool was renamed.","by":"writer"},"publishedAt":"2026-10-28T14:11:15.586Z","updatedAt":"2026-10-28T16:17:41.525Z","status":"in_effect","tone":"broken","url":"https://www.okapi.bot/providers/atlassian-mcp/breaking-changes/the-findjiraissueassignableusers-tool-stops-working/"}]}