Suggest a server AI tools directory →

Bitbucket MCP server

Last verified: 2026-09

Repos and PRs on Bitbucket Cloud.

Community Developer tools Needs a secret Claude Desktop, Cursor, Windsurf, Claude Code, VS Code

What it does

Community Bitbucket Cloud wrapper: repositories, pull requests, pipelines. The originally listed repo has gone missing — confirm the npm package and GitHub URL before you put an app password in it.

It sits in Developer tools: Split this category in two.

Good for

  • List repos in one workspace after you have verified the package still exists.
  • Read PRs and pipelines on Bitbucket Cloud.
  • Keep merge/trigger tools off until the repo URL is a live GitHub project.
  • Skip it entirely if the code already moved to GitHub or GitLab.

Tools

  • repositories / branches / commits — Read the workspace.
  • pull requests / comments / merge — PR flow when the package exposes writes.
  • pipelines — List or trigger builds.

Config (Claude Desktop / Cursor / Windsurf)

Paste the JSON below. Same mcpServers shape. Replace placeholder paths and secrets. Windows paths look like C:\\Users\\you\\project, not /path/to. Host-side steps →

Claude Desktop

OSConfig file
macOS~/Library/Application Support/Claude/claude_desktop_config.json
Windows%APPDATA%\Claude\claude_desktop_config.json (usually C:\Users\<you>\AppData\Roaming\Claude\)
Linux~/.config/Claude/claude_desktop_config.json

Cursor

ScopemacOS / LinuxWindows
This project.cursor/mcp.json in the repo root
This user~/.cursor/mcp.json %USERPROFILE%\.cursor\mcp.json

Windsurf

OSConfig file
macOS / Linux~/.codeium/windsurf/mcp_config.json
Windows%USERPROFILE%\.codeium\windsurf\mcp_config.json
{
  "mcpServers": {
    "bitbucket": {
      "command": "npx",
      "args": [
        "-y",
        "bitbucket-mcp"
      ],
      "env": {
        "BITBUCKET_USERNAME": "...",
        "BITBUCKET_APP_PASSWORD": "..."
      }
    }
  }
}

Windsurf remote MCP: use serverUrl instead of url if the block below is HTTP.

One-liner: npx -y bitbucket-mcp

Secrets it wants: BITBUCKET_USERNAME, BITBUCKET_APP_PASSWORD

Source repo →

How to get started

  1. Create a Bitbucket app password with the repo scopes you actually need.
  2. Verify the package still matches a live GitHub repo, then paste the JSON.
  3. Ask it to list repos in one workspace.

Access risk

An app password is account access. Merge and pipeline tools can ship code.

When to skip it

Skip it if the code is on GitHub/GitLab. Do not install a Bitbucket MCP whose repo 404s.

Instead: GitHub, GitLab, Git.

Vs alternatives

ServerOfficial?Needs a secret?Best for
BitbucketNoYesRepos and PRs on Bitbucket Cloud.
GitHubYesYesRepos, issues, PRs, and file contents on GitHub.
GitLabYesYesProjects, issues, and merge requests on GitLab.
GitYesNoRead a local git repo: log, diff, status.

More in Developer tools

All 18 in this category →

FAQ

The listed GitHub repo 404s — now what?

Do not install a Bitbucket MCP whose source you cannot read. Find a live package (or use Git locally) before you put an app password in env.

App password scopes?

Repo read to start. Merge and pipeline write can ship code.

Bitbucket or Git?

Git if you have a local clone. Bitbucket MCP for PRs/pipelines in the cloud.

Cloud or Server/DC?

Most community servers are Bitbucket Cloud API v2. Confirm before pointing at self-hosted.