Github Registry Rovo MCP entry points to /v1/mcp but guidance suggest /v1/mcp/authv2

Nick Siebert

The GitHub MCP Registry entry for the Atlassian Rovo MCP Server advertises a stale endpoint. The remotes block points to the legacy /v1/mcp path, but Atlassian's current getting-started guidance recommends /v1/mcp/authv2. For organizations whose policy forces MCP clients to consume server definitions directly from the GitHub MCP Registry (no manual URL overrides), this drift causes the OAuth 2.1 flow to fail, forcing a fallback to API-token authentication.

The discrepancy

GitHub MCP Registry — com.atlassian/atlassian-mcp-server, version 1.1.1 (is_latest: true):

Source: <a href="https://api.mcp.github.com/v0/servers/search?q=atlassian" target="_blank" rel="nofollow noopener noreferrer">https://api.mcp.github.com/v0/servers/search?q=atlassian</a>

Atlassian's official getting-started doc (current banner at top of page):

After 30th June 2026, usage of <a href="https://mcp.atlassian.com/v1/sse" target="_blank" rel="nofollow noopener noreferrer">https://mcp.atlassian.com/v1/sse</a> as a server endpoint will no longer be supported. We recommend updating any configured custom clients to point to /mcp: <a href="https://mcp.atlassian.com/v1/mcp/authv2" target="_blank" rel="nofollow noopener noreferrer">https://mcp.atlassian.com/v1/mcp/authv2</a>

Source: https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/

The README embedded inside the registry entry itself also still references <a href="https://mcp.atlassian.com/v1/mcp" target="_blank" rel="nofollow noopener noreferrer">https://mcp.atlassian.com/v1/mcp</a>, so the metadata appears to predate the authv2 rollout.

Impact

• Clients pinned to the registry entry connect to /v1/mcp and the OAuth 2.1 dynamic client registration handshake fails.
• Only workaround is falling back to API-token auth, which many orgs gate or prefer to avoid for interactive use.
• Organizations that mandate sourcing MCP definitions from the GitHub MCP Registry cannot override the URL locally, so they have no client-side remediation.

Expected

The registry entry's remotes should advertise <a href="https://mcp.atlassian.com/v1/mcp/authv2" target="_blank" rel="nofollow noopener noreferrer">https://mcp.atlassian.com/v1/mcp/authv2</a> (and update the embedded README) so registry-pinned clients use the current OAuth flow.

Request

Can we get Github's com.atlassian/atlassian-mcp-server registry entry, managed by Atlassian with the authv2 endpoint and a process for keeping this updated?

Jatin K Malik

Hi Nick, thanks for the detailed report and for clearly outlining the impact.

We’ve updated the GitHub MCP Registry entry for com.atlassian/atlassian-mcp-server. The latest registry version is now 1.1.2, and the registry metadata now includes the current OAuth 2.1 endpoint:

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

The embedded README/metadata has also been refreshed so registry-pinned clients should now be able to discover the authv2 endpoint directly from the GitHub MCP Registry, without requiring a manual URL override.

You can verify the updated entry here:

https://api.mcp.github.com/v0/servers/search?q=atlassian

Could you please retry from your registry-pinned client when you get a chance? If your client still selects the older /v1/mcp remote by default, please let us know which client and version you’re using so we can investigate whether any additional metadata or ordering changes are needed.

Thanks again for raising this.