nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

[😣Help] Atlassian MCP is authenticated but cannot connect or be used with Claude Code [ofid_b2c61d]

Frank Alberto Broche Gómez

Hi guys i need some help, since a few hours i cannot use the Atlassian MCP to edit on confluence. I did the authentication on the claude.ia and in the CLI but nothing works.

Sharing some pics:

Accepted answers

Artyom Karpets _ArtUp Labs_

Frank, your first screenshot shows the same error in the claude.ai web app, which does not depend on the Claude Code version, so the 2.1.305 to 2.1.306 update is unlikely to be the cause. With three of you hitting it at the same time, I'd expect it to clear on the server side; the direct claude mcp add test above will tell you which side it is.

Reynold

Same failure from Cursor, so this is not limited to Claude.

Cursor is connected to the Atlassian Rovo MCP server at https://mcp.atlassian.com/v1/mcp/authv2. On 21 Oct 2026, from about 14:05 to 14:22 UTC, the session authenticated and the connection eventually opened, then listing tools and resources timed out. Cursor marked those timeouts as unrelated to authentication. After that the stream failed and later requests returned Cloudflare 524 (origin timed out).

An unauthenticated POST to the same host returns HTTP 401 in well under a second, so the edge is up. The hang starts only after a valid login, when the server is asked for tools. The Rovo status page still shows MCP as operational.

All comments

mmartz-sonatype

Same here, it also took me three tries to re-authenticate (though I probably didn't need to). However, even after authenticating the mcp will not connect.

Gracia, Chris

Same issue here

Artyom Karpets _ArtUp Labs_

Hi Frank, from your screenshots the OAuth step works (the connector is authorized and shows "connected"), but the server does not answer the tools request within 30 seconds. Claude Code lists it as "claude.ai Atlassian MCP", which means it reuses the claude.ai connector, so the failure in claude.ai and in the CLI is one problem, not two. Two more people in this thread report the same error within minutes, which points to the service side rather than your setup. Neither the Atlassian nor the Claude status page showed an incident when I checked, so it may simply not be posted yet.

What you can try in the meantime, quickest first:

In Claude Code: /mcp > claude.ai Atlassian MCP > Clear authentication, then Reconnect. In claude.ai, disconnect and reconnect the connector, so a fresh OAuth consent is made.
Test the server without the claude.ai connector: add it directly to Claude Code with the command from Atlassian's page "Getting started with the Atlassian Rovo MCP Server" (claude mcp add --transport http atlassian followed by the server URL given there), then run /mcp and authenticate. If this one also times out, the problem is on the Atlassian side or in your network (a proxy or firewall that blocks the mcp.atlassian domain). If it works, the problem is the claude.ai connector, and the reference from your error (ofid_…) is what Anthropic support will ask for.
If you are not the site admin, ask whether your organization restricts the Rovo MCP server. Less likely here because you get a timeout rather than a refusal, but it is a quick check.

Drafted with an AI assistant and reviewed by me.

Frank Alberto Broche Gómez

@mmartz-sonatype @Gracia, Chris hey guys thanks for the answer i just noticed that my claude updated recently from v2.1.305to the v2.1.306 idk if this is related to.

Artyom Karpets _ArtUp Labs_

Frank Alberto Broche Gómez

Thanksss so much for the quick support @Karpets Artyom i will try! 🔧

have a nice day will let u know if it works for me

mmartz-sonatype

I just updated my claude code this morning as well. I also checked the claude plugin in visual studio code, in case that worked since it hasn't been updated but the connection times out there. I don't know if that plugin just uses the same claude underneath though.

Frank Alberto Broche Gómez

Hi again @Karpets Artyom same issue using the direct connector looks like is on the service side

Black screen while trying to load the auth page:

I asked claude to sent an unauthenticated request straight to the Rovo MCP endpoint from the same machine to test if there was something blocking my network access:

curl -X POST https://mcp.atlassian.com/v2/mcp -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{}'
→ HTTP 401 in 0.19s

Frank Alberto Broche Gómez

hi @mmartz-sonatype, yes looks like is on the service side T_T

Gordon Tyler

Same here. I had Atlassian MCP connector working in Claude Code Desktop and then about an hour ago requests stopped working. I tried disconnecting and reconnecting the connector but the Atlassian website auth step just loads a blank page after clicking continue.

Reynold

Same failure from Cursor, so this is not limited to Claude.

Brett Schmoll

+1 - Same issue as reported. Previously working config is now not working and timing out when attempting to restore the connection.

Reynold

Update: reconnecting from Cursor now fails in Atlassian Identity itself, before the OAuth callback returns to Cursor. The auth page shows server_error / “There seems to be an issue with your identity provider.” Atlassian request ID: 54735b68-3d27-e61b-9711-6bc9c3f9369e (around 15:25 UTC, 21 Oct). This appears broader than MCP tool discovery.

Brett Schmoll

Your account was authorized, but Atlassian didn’t respond. Check that the server is reachable and try again. If this persists, share this reference with support: “ofid_53bf1fc42e370ea8”

Reynold

https://rovo.status.atlassian.com/

Reynold

https://rovo.status.atlassian.com/

They are investigating.

Abhishekgr897

same issue i tried with both claude and chatgpt not working. it was working few hours back

Gordon Tyler

I'm still failing to authorize the connector. After clicking continue in the browser, it loads a https://auth.atlassian.com/consent URL which produces a blank page and nothing more.