Atlassian Claude Connector failing to connect

[Richard Baysa]

Hi All - running into the same issue reported in a few other recent threads here, hoping to add data points and see if anyone has found a working fix.

Clicking Atlassian Connector to Connect in Claude redirects to auth.atlassian.com/consent, and instead of the consent/scopes screen, it immediately shows:

Something went wrong
Invalid context provided. Please try authorizing again.

No token is ever issued.

Troubleshooting completed (all unsuccessful):

• Cleared cookies/site data for atlassian.com and claude.ai
• Tried in incognito (single clean session, no cached cookies)
• Tried an entirely different browser
• Checked Microsoft Entra ID sign-in logs for the Atlassian and Anthropic app registrations during failed attempts — all show Success, error code 0, Conditional Access: Success. Rules out our tenant identity/CA config.
• Confirmed the connector is active and correctly configured on the Claude admin side (Directory → Connectors → Atlassian Rovo → Configuration) — tool permissions rendering normally, nothing disabled
• Fully revoked the existing "Atlassian MCP" grant at id.atlassian.com/manage-profile/apps and reauthorized from scratch — same error, still fails

Has anyone found an actual fix (not just a self-resolving one), or is Atlassian support the only path forward right now? I don't currently have admin/billing rights on our site to open a formal support ticket directly, so posting here in the meantime while that gets sorted internally. Appreciate any insight.

[Wordsofwonders]

It sounds like you’ve already ruled out most of the usual client-side and identity-related causes. Since the Entra sign-in succeeds, the connector is active in Claude, and a full revocation/reauthorization produces the same “Invalid context provided” error, this looks more like an OAuth/Atlassian-side issue than a browser or tenant configuration problem.

I’d check whether the issue is specific to your Atlassian organization/site or affects other users as well. If multiple users get the same error across different browsers and accounts, that would be strong evidence of a service-side problem.

If anyone has found a workaround that actually resolves the OAuth context error rather than temporarily resolving itself, I’d be interested to hear it. While troubleshooting, a quick break with wordsofwonders.io might at least provide a distraction.

[Maksym Liutyi]

Hi @Richard Baysa

Sorry you’re facing this issue. I created a support ticket for you - JST-1331936. Check your email for further updates.

In the meantime, you're welcome to try the following steps on your own — they may help resolve the issue (Org Admin access required):

1. Go to admin.atlassian.com → select your organization

2. Navigate to the Rovo MCP Server settings page

3. Copy the current MCP server URL displayed there

4. In Claude: remove the existing Atlassian connector, then re-add it using the URL from step 3

5. Attempt authorization again
   
   

Best regards,
Maksym

[Richard Baysa]

Maksym - the problem I have is on Claude I can only use the "connect" or browse connectors.   I can't add a URL then connect to it.

[Richard Baysa]

Someone from support already reached out to me but thank you for suggesting some fix. 

[Sebastian Krzewiński]

Hi @Richard Baysa 

I requested Atlassian support assistance for this case. They will be able to review logs for it.

Regards,

Seba

[Richard Baysa]

Thank you!