OAuth or app password?

Both are supported. App passwords are simpler to set up for personal automations; OAuth is recommended for shared installations because tokens carry user-level audit trails.

Does it support Bitbucket Server?

No — only Bitbucket Cloud. The Server (self-hosted) API differs in URL shape and pagination; a separate server-specific MCP is required.

Can the agent fail a Pipelines build?

It can read status and trigger reruns, but it cannot mark a build as failed. Build status is sourced from the Pipelines runners themselves.

Bitbucket

Name: Top MCPs — curated MCP directory
Creator: Top MCPs
License: https://creativecommons.org/licenses/by/4.0/

Official

Manage Bitbucket Cloud repos, pipelines, and pull requests from an AI agent.

Score 64(?)AtlassianApache-2.0Verified Jun 2, 2026Top MCPs for Git & Repo Workflows →

Install View on GitHub

Quick answer

What it does

Wraps the Bitbucket Cloud REST API for repository, PR, branch, and Pipelines operations. Read-only by default; writes require explicit per-tool gates.

Best for

Atlassian-stack teams
PR triage and review on Bitbucket
Pipelines failure investigation
Branch restriction audits

Not for

Bitbucket Server self-hosted
Teams already on GitHub or GitLab (use those MCPs)

Setup recipe

Pick your client, then follow the three steps.

Install

claude_desktop_config.jsonjson

{
  "mcpServers": {
    "bitbucket": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "BITBUCKET_USERNAME",
        "-e",
        "BITBUCKET_APP_PASSWORD",
        "-e",
        "BITBUCKET_WORKSPACE",
        "ghcr.io/atlassian/mcp-server-atlassian:latest"
      ],
      "env": {
        "BITBUCKET_USERNAME": "${BITBUCKET_USERNAME}",
        "BITBUCKET_APP_PASSWORD": "${BITBUCKET_APP_PASSWORD}",
        "BITBUCKET_WORKSPACE": "${BITBUCKET_WORKSPACE}"
      }
    }
  }
}

Paste under mcpServers. Fully quit and reopen Claude after editing.

CLI or .mcp.jsonshell

# export BITBUCKET_USERNAME=reader
# export BITBUCKET_APP_PASSWORD=changeme
# export BITBUCKET_WORKSPACE=my-team
claude mcp add bitbucket -- docker run --rm -i -e BITBUCKET_USERNAME -e BITBUCKET_APP_PASSWORD -e BITBUCKET_WORKSPACE ghcr.io/atlassian/mcp-server-atlassian:latest

Run from your repo. Commit .mcp.json to share with your team.

.cursor/mcp.jsonjson

{
  "mcpServers": {
    "bitbucket": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "BITBUCKET_USERNAME",
        "-e",
        "BITBUCKET_APP_PASSWORD",
        "-e",
        "BITBUCKET_WORKSPACE",
        "ghcr.io/atlassian/mcp-server-atlassian:latest"
      ],
      "env": {
        "BITBUCKET_USERNAME": "${BITBUCKET_USERNAME}",
        "BITBUCKET_APP_PASSWORD": "${BITBUCKET_APP_PASSWORD}",
        "BITBUCKET_WORKSPACE": "${BITBUCKET_WORKSPACE}"
      }
    }
  }
}

Global path: ~/.cursor/mcp.json. Reload window after editing.

.vscode/mcp.jsonjsonc

{
  "servers": {
    "bitbucket": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "BITBUCKET_USERNAME",
        "-e",
        "BITBUCKET_APP_PASSWORD",
        "-e",
        "BITBUCKET_WORKSPACE",
        "ghcr.io/atlassian/mcp-server-atlassian:latest"
      ],
      "env": {
        "BITBUCKET_USERNAME": "${BITBUCKET_USERNAME}",
        "BITBUCKET_APP_PASSWORD": "${BITBUCKET_APP_PASSWORD}",
        "BITBUCKET_WORKSPACE": "${BITBUCKET_WORKSPACE}"
      }
    }
  }
}

VS Code uses the "servers" key (not "mcpServers").

~/.codeium/windsurf/mcp_config.jsonjson

{
  "mcpServers": {
    "bitbucket": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "BITBUCKET_USERNAME",
        "-e",
        "BITBUCKET_APP_PASSWORD",
        "-e",
        "BITBUCKET_WORKSPACE",
        "ghcr.io/atlassian/mcp-server-atlassian:latest"
      ],
      "env": {
        "BITBUCKET_USERNAME": "${BITBUCKET_USERNAME}",
        "BITBUCKET_APP_PASSWORD": "${BITBUCKET_APP_PASSWORD}",
        "BITBUCKET_WORKSPACE": "${BITBUCKET_WORKSPACE}"
      }
    }
  }
}

Open via Cascade → hammer icon → Configure.

cline_mcp_settings.jsonjson

{
  "mcpServers": {
    "bitbucket": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "BITBUCKET_USERNAME",
        "-e",
        "BITBUCKET_APP_PASSWORD",
        "-e",
        "BITBUCKET_WORKSPACE",
        "ghcr.io/atlassian/mcp-server-atlassian:latest"
      ],
      "env": {
        "BITBUCKET_USERNAME": "${BITBUCKET_USERNAME}",
        "BITBUCKET_APP_PASSWORD": "${BITBUCKET_APP_PASSWORD}",
        "BITBUCKET_WORKSPACE": "${BITBUCKET_WORKSPACE}"
      }
    }
  }
}

Open via the Cline sidebar → MCP Servers → Edit.

~/.continue/config.jsonjson

{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "docker",
          "args": [
            "run",
            "--rm",
            "-i",
            "-e",
            "BITBUCKET_USERNAME",
            "-e",
            "BITBUCKET_APP_PASSWORD",
            "-e",
            "BITBUCKET_WORKSPACE",
            "ghcr.io/atlassian/mcp-server-atlassian:latest"
          ],
          "env": {
            "BITBUCKET_USERNAME": "${BITBUCKET_USERNAME}",
            "BITBUCKET_APP_PASSWORD": "${BITBUCKET_APP_PASSWORD}",
            "BITBUCKET_WORKSPACE": "${BITBUCKET_WORKSPACE}"
          }
        }
      }
    ]
  }
}

Continue uses modelContextProtocolServers with a transport block.

~/.codex/config.tomlshell

# ~/.codex/config.toml
[mcp_servers.bitbucket]
command = "docker"
args = [
  "run",
  "--rm",
  "-i",
  "-e",
  "BITBUCKET_USERNAME",
  "-e",
  "BITBUCKET_APP_PASSWORD",
  "-e",
  "BITBUCKET_WORKSPACE",
  "ghcr.io/atlassian/mcp-server-atlassian:latest",
]
env = { BITBUCKET_USERNAME = "${BITBUCKET_USERNAME}", BITBUCKET_APP_PASSWORD = "${BITBUCKET_APP_PASSWORD}", BITBUCKET_WORKSPACE = "${BITBUCKET_WORKSPACE}" }

Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.

~/.config/zed/settings.jsonjsonc

{
  "context_servers": {
    "bitbucket": {
      "command": {
        "path": "docker",
        "args": [
          "run",
          "--rm",
          "-i",
          "-e",
          "BITBUCKET_USERNAME",
          "-e",
          "BITBUCKET_APP_PASSWORD",
          "-e",
          "BITBUCKET_WORKSPACE",
          "ghcr.io/atlassian/mcp-server-atlassian:latest"
        ]
      },
      "env": {
        "BITBUCKET_USERNAME": "${BITBUCKET_USERNAME}",
        "BITBUCKET_APP_PASSWORD": "${BITBUCKET_APP_PASSWORD}",
        "BITBUCKET_WORKSPACE": "${BITBUCKET_WORKSPACE}"
      }
    }
  }
}

Zed calls them "context_servers". Settings live-reload on save.

ChatGPT → Apps directorynone

Bitbucket doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.

2
Set required secrets
Set BITBUCKET_USERNAME, BITBUCKET_APP_PASSWORD, BITBUCKET_WORKSPACE in your shell environment before launching your MCP client.
3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.

Tools & permissions

Tool	Description	Args	Side effects
`list_repos`	List repositories in a workspace.	workspace: string	Read
`get_pull_request`	Return metadata, files, and reviewers for a PR.	workspace: string, repo: string, id: number	Read
`list_pipelines`	List recent Pipelines runs for a repo.	workspace: string, repo: string	Read
`create_comment`	Add a comment on a PR. Requires write scope.	pr_id: number, body: string	Write

Security & scope

Access scope: Read-only
Sandbox: Authenticates with a Bitbucket app password or OAuth token scoped to the smallest set of permissions the workflow needs. The MCP defaults to read-only tools.
Gotchas: App passwords with admin scope can delete branches; scope them to repo:read for agent use.
OAuth grants are workspace-wide — review which workspaces you authorise before consent.
Bitbucket rate-limits at 1000 requests/hour per user; a chatty agent can exhaust the budget on large workspaces.

Agent prompt pack

— copy into Claude, Cursor, or ChatGPT.

Paste into Claude, Cursor, or ChatGPT. Edit the [brackets] before sending.

Recommend the best MCP servers for [task: e.g. git & repo workflows work] in [client: Claude].

Constraints:
- Prefer tools that are [official | open-source | read-only] — pick what matters for my use case.
- Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport].
- Return at most 3 picks, ranked.

For each pick include:
1. One-sentence rationale.
2. The ready-to-paste install snippet for my client.
3. Any required secrets I need to create before installing.

Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-git-repo-workflows

Compare Bitbucket against a real alternative. Swap the second MCP in [brackets] if you want a different match.

Compare Bitbucket MCP vs [GitHub MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"].

Judge them on:
- Setup time and complexity (what a new user hits first).
- Auth model (none / API key / OAuth 2.1) and credential risk.
- Transport (stdio / Streamable HTTP / SSE) and where the server runs.
- Required secrets and the blast radius if they leak.
- Operational risk in an unattended agent loop.
- Which one is "good enough" for a weekend prototype vs. production.

End with one sentence: which should I pick for my scenario, which is: [my scenario].

References:
- https://top-mcps.com/mcp/bitbucket
- top-mcps.com listing for GitHub

Asks the agent to install and verify. Works inside Claude Code, Cursor Agent, Codex CLI.

Install the Bitbucket MCP server for my [client: Claude] at the default config path for that client.

Use the exact install snippet published at https://top-mcps.com/mcp/bitbucket (fetch https://top-mcps.com/mcp/bitbucket.json for the canonical server.json if you can read URLs).

Before finishing:
1. Create the required secrets (BITBUCKET_USERNAME, BITBUCKET_APP_PASSWORD, BITBUCKET_WORKSPACE) and put them in the appropriate env block — do not hard-code them.
2. Restart or reload the client so it picks up the new server.
3. Verify the server is connected (green / running state) and at least one tool is listed.
4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry.

Confirm when done and list the tools the server now exposes.

Frequently asked questions

What changed

— 2 updates tracked.

Jun 2, 2026
Refreshed install snippets and fact sheet; verified for 2026.
Apr 10, 2025
Initial directory listing.

More Git & Repo Workflows MCPs

Other tools in the same category worth evaluating.

GitHub

Official

Full GitHub API access: repos, PRs, issues, and code search.

gitgithubreposprs

5 minLow

GitLab

Full GitLab API access: repos, MRs, issues, pipelines, and registries.

gitgitlabreposmrs

5 minLow

Git

Official

Local Git operations: commit, diff, log, branch, and more.

gitlocalcommitsdiff

2 minLow

Compared with Bitbucket

Side-by-side breakdowns for the choices people most often weigh against this MCP.

BitbucketvsGitHub BitbucketvsGitLab BitbucketvsGitea BitbucketvsGit

Exploring Top MCPs for Git & Repo Workflows? See all Git & Repo Workflows MCPs →

Quick answer

What it does

Best for

Not for

Setup recipe

Install

Set required secrets

Try a minimum working prompt

Tools & permissions

Security & scope

Agent prompt pack

Full details

Frequently asked questions

OAuth or app password?

Does it support Bitbucket Server?

Can the agent fail a Pipelines build?

What changed

More Git & Repo Workflows MCPs

GitHub

GitLab

Git

Compared with Bitbucket