I couldn't connect to Atlassian Rovo from Claude AI

[Arsenia Cabrera]

From Claude AI, I couldn't connect to Atlassian Rovo. After clicking the Connect button, it redirects the page to Atlassian but then shows 'Something went wrong" on screen and to raise a support request. 

[Hamza Chundrigar]

Hi @Arsenia Cabrera

Welcome to the Atlassian Community!

Hmm, did the message Something went wrong appear during the Atlassian authorization flow, or only after you tried to submit the Atlassian Support request?

Hmm, I think a Jira board URL is fine if the Atlassian Support form asked for the affected URL, but AFAIK it shouldn’t be used as the MCP server URL in Claude. If you’re adding the connection manually, Atlassian’s current MCP server URL is:

•  https://mcp.atlassian.com/v1/mcp/authv2

After that, Claude should send you through the Atlassian OAuth authorization screen, where you approve access to your Atlassian Cloud site.

If the URL is correct and the error happens after the Atlassian authorization screen, I’d ask your organization admin to check the Rovo MCP settings. The path is Atlassian Administration, then Rovo, then Rovo MCP server. Claude’s domains, claude.ai and claude.com, are listed by Atlassian as supported domains, but an admin can still block Atlassian-supported domains or restrict access to specific trusted domains.

The other setting I’d check is IP allowlisting. Atlassian says the OAuth screen can still appear even when later MCP calls fail because the user, network, or AI tool IP isn’t allowed.

[Arsenia Cabrera]

This error message below appeared during the Atlassian authorization flow, after clicking the Connect button.

Something went wrong

Raise a support request

Invalid context provided. Please try authorizing again.

Also, the connector URL showing in the Atlassian Rovo connector detail page in the Claude.ai Directory panel is:

https://mcp.atlassian.com/v1/mcp

[Hamza Chundrigar]

Ah...ok, Atlassian documents /v1/mcp as the MCP endpoint used with OAuth, while /v1/mcp/authv2 is commonly for manual client setup. So if you selected Atlassian Rovo from Claude’s connector directory, then that makes sense.

As silly as this might sound, but have you tried running an authorization attempt in an incognito window?

1. Sign out of Atlassian in the browser.
2. Sign out of Claude.
3. Open a private/incognito window.
4. Sign in to Jira first with the Atlassian account that should have access.
5. Go back to Claude and reconnect the Atlassian Rovo connector

If the same error appears in a clean browser session, I’d also check through your organization admin to check Atlassian Administration, then Rovo, then Rovo MCP server. OAuth clients also have to be allowed by domain, and the MCP server permissions are controlled from that Rovo MCP server area for what its worth (though I have a feeling it should already be allowed).

At that point, this is likely something you'll want to raise a ticket with Atlassian Support (if you haven't already) as they may need to trace from the OAuth side.

[Arsenia Cabrera]

I've selected technical issues from the dropdown, then selected Atlassian Rovo MCP Server, entered the requested jira board URL, then "Something went wrong" We're moving mountains to get it sorted" occurred on screen. 

[Darcy Leo]

I am also facing a similar issue with Atlassian Rovo integration in Claude. The connection works, but tool actions are not always returning results from Jira or Confluence. I have tried reconnecting but the problem still continues. Has anyone found a fix or workaround?