Atlassian MCP OAuth flow gets stuck on the consent screen and stopped working suddenly today

[Vitali Tarasow]

Since today, the Atlassian MCP integration stopped working unexpectedly during an active chat session.

When I try to authorize the app, the OAuth page shows:

“Atlassian MCP is requesting access to your Atlassian account.”

After that, the progress ring keeps spinning indefinitely and the flow never completes.
The authorization fails in Claude Desktop with the message:

“Authorization with the MCP server failed. You can check your credentials and permissions. If this persists, share this reference with support: ofid_9ba90d073f455a49”

I already tried:

• reconnecting the integration,

• removing and re-adding the connection,

• restarting Claude Desktop multiple times,

• testing in the browser,

• deleting the browser cache in Chrome,

• trying again with Microsoft Edge.

None of that fixed the issue.

The interesting part is that it still works in Claude CLI, but not in the browser/desktop flow. That makes it look like an OAuth redirect or session issue specific to the desktop/browser authorization path.

Expected behavior
The Atlassian OAuth consent flow should complete successfully and return me to the app with a working MCP connection.

Actual behavior
The consent screen stays stuck loading forever and the authorization never completes.

Environment

• Claude Desktop on Windows

• Atlassian MCP endpoint: mcp.atlassian.com/v1/mcp

• Issue started suddenly today

• Works in Claude CLI, fails in browser/Desktop

[Arkadiusz Wroblewski · Accepted solution]

Hello and welcome to the Community @Vitali Tarasow 

Hm... It looks like the desktop/browser OAuth callback path problem.

Atlassian’s MCP troubleshooting guide calls out this exact pattern as an OAuth loop / redirect issue and says to make sure http://localhost:3334 is allowed in the browser and firewall settings.

https://support.atlassian.com/atlassian-rovo-mcp-server/docs/troubleshooting-and-verifying-your-setup/

If localhost:3334 is allowed and it still hangs, this is one for Atlassian Support. Include the reference ID ofid_9ba90d073f455a49.

[Vitali Tarasow]

thanks a lot for your help and for pointing me in the right direction.
The MCP is working again now — it seems it was just a small hiccup after all.

[Arkadiusz Wroblewski]

@Vitali Tarasow 

Glad it working. Sometimes just happen 🤠