failed to reconnect to rovo mcp after endpoint update

[Viktor Makarevich]

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.

[Dr Valeri Colon _Connect Centric_]

@Viktor Makarevich /authv2 is for the OAuth 2.1/DCR authorization flow, not a drop-in replacement for the MCP server URL. Many clients should still connect to https://mcp.atlassian.com/v1/mcp and let the MCP client/proxy handle auth negotiation. If the tool requires a single server URL, try reverting the server URL to /v1/mcp, clearing the saved OAuth session, and reauthorizing.

[Rebekka Heilmann _viadee_]

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]

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_]

@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]

Oauth2 used