Forums

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

Not able to connect to bitbucket workspace using ROVO MCP server in VS Code

Tanuja Walgude
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!
April 30, 2026

I have installed the Atlassian MCP server from VS Code extensions and add below configurations in mcp.json file:

 

"com.atlassian/atlassian-mcp-server": {
            "type": "http",
            "url": "https://mcp.atlassian.com/v1/mcp",
            "gallery": "https://api.mcp.github.com",
            "version": "1.1.1",
            "headers": {
                "Authorization": "Basic <API_TOKEN>"
            }
        }
The API token is generated from link - https://id.atlassian.com/manage-profile/security/api-tokens with API token app as Rovo MCP. I have tried giving all permissions available to make sure its not permission issue. with this I am trying github copilot to query bitbucket pull requests. Getting below error:
We are having trouble verifying your organization permissions. Please try again shortly.
When tried using OAuth2, the jira is getting connected and fetching task.
Need to connect to bitbucket cloud using MCP to utiize github copilot

1 answer

0 votes
Ajay _view26_
Community Champion
April 30, 2026

Hi @Tanuja Walgude 

Welcome to the Community!

The MCP server currently authenticates org-level permissions via OAuth, not Basic auth with API tokens, even if you've granted every available scope on the token.

The root cause is that API tokens generated at id.atlassian.com work fine for Jira REST calls but the Rovo MCP server's Bitbucket integration requires an OAuth 2.0 flow to verify workspace membership and permissions. That's exactly why Jira connects fine for you via OAuth but Bitbucket doesn't via Basic auth.

The fix is to switch from Basic auth to OAuth2 in your mcp.json. Remove the Authorization header entirely and instead follow the OAuth2 setup in the Atlassian MCP docs — you'll get a browser prompt the first time to grant workspace access, after which the token is cached. Once connected via OAuth, GitHub Copilot should be able to query Bitbucket PRs without issues.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin Site Admin
TAGS
AUG Leaders

Atlassian Community Events