Atlassian Rovo MCP is unable to read Jira issue

[Scott Moore]

I've used the Rovo MCP many times to read Jira issues. 

However, today I:

1. Launched Claude, it opened a browser to go through auth at https://mcp.atlassian.com/v1/authorize
2. Went through the auth flow in my browser, it said "Authorization successful! You may close this window and return to the CLI."
3. Tried to use the MCP within a Claude session to read a Jira issue

It failed. I've done the above four times now, with a some variation in how I tried to re-auth in between (either reconnecting the MCP from within the session using /mcp, or by re-launching the session).

Here is the Claude reply from my fourth try:

"Still no — /mcp is reporting Failed to reconnect to atlassian: -32000, which means the standalone Rovo MCP server isn't
running. Its getJiraIssue tool is not registered in this session, so I literally have no way to call it.

The -32000 is a JSON-RPC server-error code coming from the MCP transport — typical causes are the server process crashing
on startup, missing/expired credentials in its config, or a stale auth cache. This needs to be fixed at the MCP server
level before I can use it."

[Dr Valeri Colon _Connect Centric_]

Hi @Scott Moore, if re-authentication succeeds but Claude still reports Failed to reconnect to atlassian: -32000, the issue is likely with the MCP connection rather than Jira access itself. A few users have recently reported MCP authentication and connectivity issues despite successful authorization. I'd check whether the Atlassian MCP server is connected in Claude, remove and re-add the integration, and if the problem persists, open an Atlassian support ticket so they can review the backend logs.

[Arkadiusz Wroblewski]

Hello @Scott Moore 

Did it worked before with same Setup ?