Bitbucket Cloud is now available on the Atlassian Rovo MCP server

[#1]

We're excited to announce that Bitbucket Cloud is now supported on the Atlassian Rovo MCP Server. Meaning AI clients like Claude, ChatGPT, Cursor, and VS Code can now browse repositories, create commits, open pull requests, and check pipeline results all through the same secure MCP connection that already works with Jira and Confluence.

Available tools and scopes

The table below lists every Bitbucket Cloud tool currently available through the Atlassian Rovo MCP Server, along with the actions each supports and the scopes required.

Tool	Action	Description	Scopes
bitbucketWorkspace	list	List all workspaces	read:workspace:bitbucket
	get	Get a specific workspace	read:workspace:bitbucket
bitbucketRepository	list	List repositories in a workspace	read:repository:bitbucket
	get	Get a specific repository	read:repository:bitbucket
bitbucketRepoContent	branch.get	Get a branch	read:repository:bitbucket
	branch.create	Create a new branch	write:repository:bitbucket  read:repository:bitbucket
	commit.create	Create a commit	write:repository:bitbucket
	commit.get	Get a specific commit	read:repository:bitbucket
	files.get	Get file/directory contents at a ref	read:repository:bitbucket
bitbucketPullRequest	create	Create a new pull request	read:pullrequest:bitbucket  write:pullrequest:bitbucket
	get	Get a specific pull request	read:pullrequest:bitbucket
	list	List pull requests	read:pullrequest:bitbucket
	comment	Add a comment to a pull request	read:pullrequest:bitbucket
	comments	List comments on a pull request	read:pullrequest:bitbucket
	diff	Get the diff of a pull request	read:pullrequest:bitbucket
	approve	Approve a pull request	read:pullrequest:bitbucket  write:pullrequest:bitbucket
	merge	Merge a pull request	read:pullrequest:bitbucket write:pullrequest:bitbucket
bitbucketPipeline	list	List pipelines	read:pipeline:bitbucket
	get	Get a specific pipeline	read:pipeline:bitbucket
	run	Trigger a pipeline	read:pipeline:bitbucket write:pipeline:bitbucket
	steps	List steps for a pipeline	read:pipeline:bitbucket
	step.get	Get a specific pipeline step	read:pipeline:bitbucket
	step.log	Get the log for a pipeline step	read:pipeline:bitbucket
bitbucketEnvironment	list	List environments	read:pipeline:bitbucket
	get	Get a specific environment	read:pipeline:bitbucket
	create	Create a specific environment	admin:pipeline:bitbucket
	update	Update an environment	admin:pipeline:bitbucket
	delete	Delete an environment	admin:pipeline:bitbucket
bitbucketDeployment	list	List deployments	read:pipeline:bitbucket
	get	Get a specific deployment	read:pipeline:bitbucket

What you can do with these tools

Here are a few examples of how these tools come together in practice:

• Explore a codebase: List workspaces and repositories, browse branches, and read file contents all from your AI client.

• Manage pull requests end to end: Create PRs, review diffs, comments, approve, and merge without switching context.

• Monitor pipelines and deployments: Check pipeline runs, view environments, and track deployments. When a build breaks, your AI client can help you trace the failing commit.

Getting started

Before starting, keep in mind that Bitbucket Cloud tools can be used only with workspaces that are connected to an Atlassian organization. If your workspace has not yet been linked, review this guide and complete this setup process. Additionally, access to Bitbucket tools is presently limited to API token authentication; OAuth is not yet supported, though it is on the roadmap and currently under development

To get set up, an org admin needs to enable API token auth in Admin Hub > Rovo > Rovo MCP. Once that's done, connect through any supported MCP client (Claude, ChatGPT, Cursor, VS Code, and others) and start using Bitbucket tools alongside Jira and Confluence.

For full setup details, visit the Atlassian Rovo MCP Server documentation.

Feedback and support

This is just the beginning, and we’re excited to develop additional tools for Bitbucket Cloud based on this foundation. Your feedback will directly influence the features we prioritize and the tools we create next. If you have ideas for new tools or encounter any problems, please leave a comment below. We are here to assist and we value your input.

[Derek Price]

This is great!  Unfortunately, I just removed my old /sse MCP and added https://mcp.atlassian.com/v1/mcp but it is not asking be about Bitbucket permissions.  Just about Jira, Confluence, and Compass, as before.  Am I missing something?

Thanks!

[Sunil Kunisetty]

Hi @Derek Price ,  That consent screen flow is for the OAuth flows and we only support those products with OAuth for now.

Currently  JSM,  BitBucket, TWG Tools are only supported with API Tokens. See the 'Getting Started' section above on how to use these tools with API Tokens.

[Samer Mansour]

I added mcp to claude as instructed on claude's official support page: https://code.claude.com/docs/en/mcp

claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp

Opened up claude and enter /mcp, selected the local just added, choose authenticate, but it takes you to the OAuth page.

Can you provide further instructions on how to go about authenticating with an api token, I have one, where do I enter it?

update: https://support.atlassian.com/atlassian-rovo-mcp-server/docs/configuring-authentication-via-api-token/

I followed the steps when I go to auth in claude, still upset, I added the mcp json to the .mcp.json in the ~/.claude folder, no dice

╭──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ Atlassian MCP Server │
│ │
│ Status: △ needs authentication │
│ Auth: ✘ not authenticated │
│ URL: https://mcp.atlassian.com/v1/mcp │
│ Config location: C:\****************\.claude.json [project: C:\**********] │
│ │
│ ❯ 1. Authenticate │
│ 2. Disable │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯

[Sunil Kunisetty]

Hi Samer,

I believe it's defaulting to the OAuth flow. Have you tried this approach for API Token flow:
_______________________________________________________________

You will need to add the Atlassian Rovo server entry to the mcpServers object in your claude_desktop_config.json.

File Location:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

• Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this entry:

JSON

"atlassian-rovo-mcp": {
    "command": "npx",
    "args": [
      "mcp-remote@latest",
      "https://mcp.atlassian.com/v1/mcp",
      "--header",
      "Authorization: Basic base64(username:password)"
    ]
  }

[Sunil Kunisetty]

This link explains API Token usage with Rovo MCP Server:

https://support.atlassian.com/atlassian-rovo-mcp-server/docs/configuring-authentication-via-api-token/

[Emmanuel Pellegrin]

when i use the API key i have only 2 tools : 

1. mcp_atlassian-rov_getTeamworkGraphContext
2. mcp_atlassian-rov_getTeamworkGraphObject

otherwise when i use with oauth I have acces to 37 tools. 

[Dilip Venkatesh]

Can you please provide more details of

- how you created the API token

- what configuration you have in your mcp.json file

Below tools are default ones, makes me believe that authentication was not set up correctly.

1. mcp_atlassian-rov_getTeamworkGraphContext
2. mcp_atlassian-rov_getTeamworkGraphObject

[Christiaan Titos Bolivar]

Great news.

We use the Atlassian MCP through Claude.ai (which are shared with Claude Code automatically). I assume the API token auth limitation means we cannot use the bitbucket tools in claude.ai using the default Atlassian connector?

[Emmanuel Pellegrin]

Hi @Dilip Venkatesh , my configuration is :

 "atlassian-rovo-mcp": {

      "url": "https://mcp.atlassian.com/v1/mcp",

      "headers": {

        "Authorization": "Basic XXXXXXXXXXXX",

      },

    },

I've created the key through  my profile-> security-> api tokens. then I encoded by executing echo -n "my_email@my_domain.com:MY_API_TOKEN_HERE" | base64

[Samer Mansour]

Yeah... I'm just gonna wait til oAuth or some other tool or plugin to come along and use that.

[Michael Rothman]

I got this working but its quite messy without it included in OAuth. Please prioritize it

[Dilip Venkatesh]

@Emmanuel Pelegrin - did you create API tokens with scopes? and select `Rovo MCP` as the product?

@Michael Rothman - we will rolling out BBC with OAuth very soon.