Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

failed to reconnect to rovo mcp after endpoint update

Viktor Makarevich
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 19, 2026

After updating the endpoint, connecting the Rovo MCP to external tools doesn't work, even if I try to connect using the org admin, although all access is granted.

1 answer

0 votes
Rebekka Heilmann _viadee_
Community Champion
May 19, 2026

Hi @Viktor Makarevich 

what do you mean by "updating the endpoint"? 

Are you the Org Admin and can check MCP settings on admin.atlassian.com? External tools may need to be added to the list by adding the domain. It all depends on what you're trying to do and what your current setup is.

Viktor Makarevich
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 19, 2026

endpoint is this: https://mcp.atlassian.com/v1/mcp/authv2. and it changed from https://mcp.atlassian.com/v1/mcp. I checked the settings under the org admin and everything is configured and access is open.

Rebekka Heilmann _viadee_
Community Champion
May 20, 2026

@Viktor Makarevich have you also updated the way you authenticate? 

Are you using Oauth2 or are you now using API tokens? Not an expert but sounds to me like the /authv2 endpoint needs to be used with Oauth authentication.

Viktor Makarevich
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 20, 2026

Oauth2 used

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events