Atlassian Rovo Mcp Remote Server for Bitbucket

[Dan Umstattd]

I have read through this document and its linked documents on how to configure and setup MCP connectivity using Rovo to hook into bitbucket. However every time I ask my github copilot agents to connect it keeps telling me that the only thing it can see is Jira, & confluence. It says it does not support bitbucket. The scoped api token with all the recommended permissions were used. The only way I can get this to work is using a powershell wrapper to store my api token as an env var and utilize this command within 'npx -y bitbucket-mcp@latest'

mcp url tried but no access to bitbucket: https://mcp.atlassian.com/v1/mcp/authv2

Thoughts?

[Germán Morales _ Hiera]

Hi @Dan Umstattd,

Two details in your post narrow this down. The endpoint you used, https://mcp.atlassian.com/v1/mcp/authv2, is the correct one for API token auth, and npx bitbucket-mcp working with that same token shows the token itself is valid against Bitbucket. So the credentials and the URL are not the problem. The "only Jira and Confluence" result is the tell: that is exactly what the connection returns when it ends up on the OAuth path, which today never includes Bitbucket. Two prerequisites and one client detail decide whether you stay on OAuth or actually reach the Bitbucket tools.

On the Atlassian side, check these in order:

• Your Bitbucket workspace is linked to an Atlassian organization. The Bitbucket Cloud tools are published only for org-linked workspaces, so a valid token will not surface them until the link exists: Linking your Bitbucket Cloud workspace to an Atlassian organization.
• An org admin has enabled API token authentication under Admin Hub > Rovo > Rovo MCP Server. While it is off, clients cannot use the header at all and silently fall back to OAuth.
• The token carries the Bitbucket scopes, not only the Jira and Confluence ones. Regenerating it with all scopes selected rules this out.

The client detail is where the Atlassian sample can mislead for Copilot. That sample uses an mcpServers block, but Copilot's MCP config expects a servers entry with type set to http, the url pointing to your authv2 endpoint, and a headers block sending Authorization: Basic base64(email:token). If the entry is malformed, Copilot falls back to OAuth and you land on Jira and Confluence only. The header format and the base64 email:token encoding are documented in Configuring authentication via API token.