I am using Atlassian MCP servers with Claude code. I installed mcp and then authenticated it. Everything is fine, authentication was successful.
But when I try to use it, for example to get issues from Jira, it returns an error.
What can be wrong?
atlassian - Get current user info (MCP)
⎿ Error: {"error":true,"message":"We are having trouble completing this action. Please try again shortly."}
⏺ atlassian - List accessible resources (MCP)
⎿ Error: Sibling tool call errored
⏺ Let me try with the plugin MCP server.
⏺ plugin:atlassian:atlassian - Get current user info (MCP)
⎿ Error: {"error":true,"message":"We are having trouble completing this action. Please try again shortly."}
⏺ plugin:atlassian:atlassian - List accessible resources (MCP)
⎿ Error: Sibling tool call errored
⏺ Both calls failed together. Let me try them individually.
⏺ plugin:atlassian:atlassian - List accessible resources (MCP)
⎿ Error: {"error":true,"message":"We are having trouble completing this action. Please try again shortly."}
⏺ atlassian - List accessible resources (MCP)
⎿ Error: {"error":true,"message":"We are having trouble completing this action. Please try again shortly."}
Everything is working fine today. It seems to have been a problem on the Atlassian side. The problem is solved, thanks
I still have the same issue - no change :/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Okay now it is working for me as well.. Confirming that issue resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I spent hours yesterday trying to debug and uninstall and reinstall and changing to npx command for mcp and removing auth and reauth a thousand times thinking it was my problem.
Since I can't find any issues online. Thankfully now I know I'm not crazy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
i'm faicing the same issue, it keeps stuck in
claude.ai Atlassian - Add comment (MCP)(cloudId: ......
Running...
✶ Schlepping… (4m 12s · ↓ 2.2k tokens · thinking)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same here. Only way to fix it so far is to exit Claude and restart.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am facing the same issue right now:
{"time":"2026-02-16T15:32:18.040564+01:00","level":"INFO","msg":"oauth MCP debug: atlassianUserInfo result","tool":"jira","isError":true,"text":"{\"error\":true,\"message\":\"We are having trouble completing this action. Please try again shortly.\"}"}
But I tested MCP server directly via MCP Proxy (skipping my API completely) and the same outcome.. So it looks like there is an issue on Atlassian MCP server or maybe some permissions missing - token was created correctly but their MCP server is rejecting it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Also maybe it can be related with this incident?
https://jira-software.status.atlassian.com/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm seeing the same issue on Node v25.5.0. The OAuth flow finishes fine, and both the MCP and tools load up, but I get a "We are having trouble completing this action" error whenever I actually try to use them. Already tried re-authenticating, but it didn't help
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I hit this too: OAuth completed and tools appeared loaded, but calls still failed because of stale local runtime/session state (not Node `v25.5.0` itself).
What helped was: kill all `mcp-remote` processes, clear the Rovo MCP auth cache (by deleting the cache dir), re-auth and start the mcp process again.
In my case I think it was related to some stale / de-synced sessions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.