Unable to connect Claude to Atlassian MCP – Invalid context error

[Mauricio Melo]

Hello Atlassian Community,

I need assistance diagnosing an issue with the Atlassian MCP connector that appears to affect only my user account.

Since June 30, following the endpoint migration from /v1/sse to /v1/mcp, I have been unable to connect Claude to Atlassian.

When I attempt to authorize the connection from Claude, the Atlassian consent page displays the following error:

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

I have already completed the following troubleshooting steps:

• Disconnected Claude from Atlassian and cleared the browser cache.
• Tested the authorization flow in an incognito window.
• Changed my network and public IP address.
• Tested using a VPN with an exit location in Colombia.
• Revoked and reauthorized the Atlassian MCP application from my account at id.atlassian.com.
• Confirmed that the Atlassian MCP application appears under Administration > Connected apps in my Atlassian environment.
• Tested connectivity using:

curl -v https://mcp.atlassian.com/v1/mcp

The endpoint returns 401 Unauthorized (invalid_token), while the TLS handshake completes successfully, confirming that the endpoint is reachable from my network.

Other users in the same Atlassian environment are able to connect successfully, so the issue appears to be specific to my account, authorization context, permissions, or site association.

Could you please verify:

• Whether my user account has access to the Atlassian MCP application.
• Whether any user-level, group-level, site-level, or application access policy is affecting my account.
• Whether the OAuth authorization context associated with my account may be invalid or incorrectly linked.
• Whether an existing authorization record needs to be manually cleared or reset on Atlassian’s side.

Best regards,
Mauricio

[Viswanathan Ramachandran]

Hi @Mauricio Melo 

Thank you for providing the steps you have tried. Additionally, have you tried the below?

• Clearing your Local OAuth Cache ?
• Revoke Existing Authorisations on Atlassian's Side ?
• If revoking or clearing cache already tried, did you check if you have permissions? you might need to check with your organisation admin.