Connect Bitbucket to Claude Code

Let Claude open pull requests and push branch changes in Bitbucket. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Bitbucket to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Bitbucket, you add a Bitbucket MCP server: a small hosted service that exposes Bitbucket's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Bitbucket account. No API keys pasted into config files.

claude mcp add --transport http bitbucket https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Bitbucket once connected?

Full read-write Bitbucket access lets Claude open a pull request from a fix, comment on an open review, push a change to a feature branch, decline or update a stale PR, and request approval once you confirm. The review and follow-up that used to mean tab-switching happen where the code already lives.

Open a pull request from a feature branch with a clear description and reviewers
Comment on an open pull request or post a review summary
Push a change to a feature branch and link it to the right pull request
Add reviewers and request approval on a pull request once you confirm
Decline or update a pull request as you triage a backlog
Create a branch from an issue or ticket to start the work

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Bitbucket access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Bitbucket API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Bitbucket changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Bitbucket connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Bitbucket connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Bitbucket account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Bitbucket's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Bitbucket?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Bitbucket account it signs in with. Revoking access is one click in Bitbucket.

More on the Bitbucket connector

Bitbucket connector for claude.ai CircleCI + Claude Code Jenkins + Claude Code Vercel + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us