Atlassian Rovo MCP + Claude Web/Desktop Suddenly Failing — Anyone Else Seeing This?

[Yung]

Hi,

Since Nov 15–16 (SGT), my Atlassian Rovo MCP integration stopped working on Claude Web and Claude Desktop, even though it worked perfectly before.

Claude Code / CLI still works normally.

I’m not a developer, but I’m an advanced user and used Claude + ChatGPT to investigate. Following their guidance, I collected HAR files, audit logs, and connector screenshots.

Here are the key findings:

✔ OAuth works

Claude Web/Desktop connect to Atlassian successfully and all MCP tools appear.

✔ Atlassian MCP receives the tool requests

Atlassian admin audit logs show tool calls like getConfluencePage, searchAtlassian, etc.
All returning HTTP 200 from Jira/Confluence.

✔ Claude Web/Desktop start tool runs

HAR files show Claude creating messages (201) and tool runs (202).

❌ Claude Web/Desktop still return a generic tool error

No output is shown even though Atlassian returns success.

✔ Claude CLI continues to work

Same Atlassian account + same MCP URL → works fine.

✔ My configuration seems correct

• “Allow Atlassian-supported domains” is ON

• Using Atlassian’s official MCP URL:
  https://mcp.atlassian.com/v1/sse

• No custom domains required

📝 I have already filed an issue with Atlassian’s Rovo MCP beta support

Here: https://customerfeedback.atlassian.net/servicedesk/customer/portal/1701/group/1762/create/11360
I have provided full details and files to them.

---

❓Questions

• Is anyone else experiencing this since Nov 15–16?

• Any known fixes or workarounds (besides CLI)?

• Did Atlassian or Claude release any updates recently?

Thanks in advance — happy to share logs privately if it helps.
— Yung

[Yung]

📄 Suggested Follow-Up Comment for Your Community Thread

If you’re experiencing the same Atlassian Rovo MCP → Claude Web/Desktop failure, I strongly encourage you to send feedback directly to the Atlassian MCP engineering team through their beta support portal:

🔗 https://customerfeedback.atlassian.net/servicedesk/customer/portal/1701/group/1762/create/11360

This goes straight to the developers who maintain the Rovo MCP Server, and they are best positioned to investigate and fix issues during the beta.

---

💡 Additional Context (for anyone who wants the technical side)

With help from Claude and ChatGPT, I collected HAR files, audit logs, and connector data and shared them with Atlassian engineering.
Based on that analysis, the leading hypothesis is:

The issue is likely caused by a regression or compatibility change in the integration between Atlassian’s Rovo MCP Server and Claude Web/Desktop’s remote connector layer.

Some supporting observations:

• OAuth works and Claude lists the toolset

• Claude Web/Desktop successfully start tool runs

• Atlassian MCP Server receives those tool runs and Jira/Confluence respond with HTTP 200

• Yet Claude Web/Desktop still show tool errors with no output

• Claude CLI continues to work, which uses a completely different, local connection path

This pattern suggests the problem is probably in a server-side or connector-side change, not something that individual users can fix.

If Atlassian and Anthropic confirm this, then the fix will have to come from them — not from local settings. It seems that there is nothing a user can do.

---

If you're affected…

Adding your report to the feedback portal above will help Atlassian gauge impact and prioritize the fix.

— Yung

[Yung]

I have raised the issue to the Claude Support team 12 Hours ago on the Claude support chat within Claude app. I have never had good experience with Claude support. They usually are not responsive even when I am a Claude Max subscriber. Atlassian Support said that they are not able to reach Claude support team 12 hours ago. Hopefully, they can reach them on Monday morning USA time. You can try raising the issue to Claude support but I don't think they have good customer service. 

[Yung]

There is nothing a user can do to fix the issue. The diagnosis is clear from Atlassian. Claude rolled out something on Fri/Sat that broke the MCP integration with SSE. They have to fix it.

It is now fixed and Claude is working again with Atlassian Rovo MCP. You do not need to do anything. This was a server side issue.

There is no use raising the issue with Claude support. They have always been unresponsive to me even as a Claude Max subscriber. As of now, they have not replied to my support message raised 36 hours ago.

Atlassian Support is much more responsive and proactive. They have confirmed that Atlassian MCP could work with Cursor (24 hours ago) and it is a Claude server side issue. Thanks so much to Dilip for his prompt and proactive responses.

--

Dilip Venkatesh commented:

Dear Customer,

**Update: Issue Resolved**

We're pleased to inform you that the integration issues have been resolved. You should now be able to use the Atlassian MCP with Claude Web and Desktop without encountering errors.

**Next Steps:**

* Please reconnect to the integration and test your workflows
* If you continue to experience any issues, please reach out to us immediately with specific details

**Technical Details:**

We've conducted a thorough investigation and confirmed that no changes or regressions occurred on the Atlassian side regarding SSE (Server-Sent Events) support. We're actively collaborating with Anthropic (Claude) to identify the root cause and implement preventative measures to ensure service reliability going forward.

**We Appreciate Your Patience**

Best regards,
Atlassian MCP Platform Team

---

This request is now completed.

Dilip Venkatesh changed the status to *Done.*

[Pete Capra]

Yep, I've also got this issue. Noted that it's better raised with the Rovo Team, not the Claude / ChatGPT team. 

[Yung]

Atlassian says it’s working with cursor. So it’s a Claude issue. 

[Yung]

It’s working now with Claude. They’ve fixed their server issue. 

[Jennifer Luo]

We are also experiencing issues since this morning (17 Nov AEDT)

[Yossi Golan]

Having the same issue here since 16.11...

[Ilya Alexandrov]

Having the same issue since 16.11

[Macaulay Hey]

Same issue

[Amichai Klipstein]

Still failing. Can't get Claude to retrieve/create Confluence Pages in Claude.ai (chrome/comet browsers)

[Luiz Carlos Padilha Junior]

Same issue here in Brazil since this morning (Nov 17, 2025 ~08:00 BRT). OAuth flow completes successfully, connector shows as connected, but every Jira tool (List Jira projects, Search with JQL, etc.) instantly fails with the red warning triangle. Already tried revoking/re-approving permissions, new API tokens, different browsers, Claude Web + Desktop → no change. Jira Cloud. Was working perfectly until Friday.

[Yossi Golan]

It begun working for me again now!
I didn't do anything, just fired a query and suddenly it works again.

[Yung]

There is nothing that Atlassian or user can do until Claude fixes their server. They rolled out something that broke the integration last Fri/ Sat. 
As of now, claude is working now with Atlassian. You don’t have to do anything. The diagnosis was clear that it’s an issue with Claude backend server. 
The issue is resolved.

[Andrei Kondratev]

There was a bug in one of MCP dependencies (@modelcontextprotocol/sdk) which had very similar symptoms. I guess claude code and claude desktop are using the same dependency. 

https://github.com/modelcontextprotocol/typescript-sdk/issues/1103

The  bug has recently been fixed in v 1.22 of mcp sdk, so hopefully this should be fixed in the next Claude release.

[Amichai Klipstein]

MCP Worked for me a few hours ago on Claude web. Down again. Can't retrieve Confluence pages.