Atlassian MCP server with Claude on multiple Bitbucket workspace

Question

When I authorize the Atlassian MCP Server (client: Claude, callback https://claude.ai/api/mcp/auth_callback), the consent screen has two fields:

* Site (For Jira, Confluence and other tools): <my-site>.atlassian.net
* Bitbucket workspace: a dropdown that lists every workspace my account belongs to (workspace-a, workspace-b)

The Bitbucket workspace dropdown is single-select (radio buttons), so I can authorize only one workspace per connection, although the list shows both and my account has access to both.

Steps to reproduce

* Belong to two or more Bitbucket workspaces with the same Atlassian account.
* Connect the Atlassian Rovo MCP Server from an MCP client such as Claude.
* On the consent screen, open the “Bitbucket workspace” dropdown.
* Try to select more than one workspace.

Expected behavior

Being able to select several Bitbucket workspaces, the same way the dropdown lists them all, so one MCP connection can work across all the workspaces I have access to.

Actual behavior

Only one workspace can be selected at a time. Granting them one after the other doesn’t work either:

* I authorize the connection with workspace-a selected and confirm. Access to workspace-a works.
* I authorize again, select workspace-b and confirm.
* Access to workspace-b now works, but the grant for workspace-a is gone: the new consent replaces the previous one instead of adding to it.

James Gamble · Accepted Answer

Hola Alberto,

What you’re seeing appears to be the current limitation, not something specific to Claude. The consent flow grants Bitbucket access to one workspace at a time, and reauthorizing the same MCP connection replaces the workspace grant rather than adding another. Atlassian

Atlassian’s current MCP documentation states that OAuth 2.1 is the primary authentication method, but I couldn’t find any documentation indicating that a single OAuth grant can include multiple Bitbucket workspaces.

One possible workaround is API token authentication if your organization allows it. Atlassian API tokens can be scoped for Bitbucket access, including workspace access, so that may be worth testing if you need one MCP client to work across multiple workspaces.

I also couldn’t find a public Atlassian feature request specifically for multi-workspace Bitbucket authorization in Rovo MCP, so I’d consider raising one with Atlassian if OAuth is the required authentication method.

Thanks,

James

Trevan Householder_Isos-Tech-Consulting_ · Accepted Answer

Hi @Alberto Borsato, @Sebastian Krzewi ński is right: with OAuth, the Rovo MCP Server only connects to one site or workspace at a time, and re-consenting swaps it rather than adding one (Atlassian KB). Multi-site support is in progress under ECO-1259, so it's worth a vote and a comment that Bitbucket workspaces need it too.

One thing to try in the meantime is API token auth, since those tokens aren't tied to a single cloud ID. I haven't confirmed it works across two Bitbucket workspaces, but it's the most promising route. Heads-up: an org admin has to enable it first, and both workspaces need to be linked to your Atlassian org.