New OAuth connections to Atlassian MCP failing with "Invalid context provided" — workspace one-bemob

Question

Problem:
New OAuth grant flows for the Atlassian MCP connector are failing. Existing connections (old grants) still work, but any attempt to create a new connection fails during the consent step with an "Invalid
context provided" error.

Steps already taken (none resolved the issue):
1. Disconnected Atlassian connector from Claude settings
2. Revoked all OAuth grants at id.atlassian.com/manage-profile/apps
3. Deleted all API tokens at id.atlassian.com/manage-profile/security/api-tokens
4. Cleared local mcp-remote cache (%USERPROFILE%\.mcp-auth)
5. Tried reconnecting via official Atlassian connector (not custom)
6. Tried custom connector with https://mcp.atlassian.com/v1/mcp/authv2
7. Used an anonymous browser window (no session reuse)
8. Workspace admin confirmed org-level settings are correctly configured

Additional context:
Issue started ~2026-06-10, possibly related to Atlassian Identity OAuth migration announced on 2026-05-27.

Steven Lone · Answer

I am also experiencing the same issue, but before I follow the Support ticket path, I was curious if anyone has already submitted one and if they have heard anything about this yet?

Dr Valeri Colon (Connect Centric) · Answer

@Ricardo Mendes @Pablo Herrera @Matthew Woolley @nick_strickland welcome all! Glad to have you here. Since multiple users are seeing this and old grants still work while new OAuth grants fail, this looks like a platform-side MCP/OAuth regression rather than a local credential/cache issue. Atlassian’s MCP docs point users to Atlassian Support for auth issues, so I’d open a support ticket and include the workspace, timestamps, connector URL, exact error, browser console/network logs, and note that several users can reproduce it.

https://support.atlassian.com/contact

Pablo Herrera · Answer

having the same issue trying to connect to https://mcp.atlassian.com/v1/mcp