I've used the Rovo MCP many times to read Jira issues.
However, today I:
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."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.