Bitbucket MCP Server

Name: Bitbucket MCP Server
Author: droplinkperformance

by droplinkperformanceversion 1.2.0i★ –iRuns on your computer

Registry nameio.github.droplinkperformance/bitbucket-mcp-server

Install

Overview

Description from the maker (original English)

Provider-agnostic, AI-review-first MCP server for Bitbucket Cloud.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: BITBUCKET_ACCESS_TOKEN, BITBUCKET_EMAIL, OPENAI_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: BITBUCKET_ACCESS_TOKEN, BITBUCKET_EMAIL, BITBUCKET_DEFAULT_WORKSPACE, LLM_PROVIDER, OPENAI_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "bitbucket": {
      "command": "npx",
      "args": [
        "-y",
        "@droplinkperformance/bitbucket-mcp-server"
      ],
      "env": {
        "BITBUCKET_ACCESS_TOKEN": "your-value",
        "BITBUCKET_EMAIL": "your-value",
        "BITBUCKET_DEFAULT_WORKSPACE": "your-value",
        "LLM_PROVIDER": "your-value",
        "OPENAI_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add bitbucket --env BITBUCKET_ACCESS_TOKEN=your-value --env BITBUCKET_EMAIL=your-value --env BITBUCKET_DEFAULT_WORKSPACE=your-value --env LLM_PROVIDER=your-value --env OPENAI_API_KEY=your-value -- npx -y @droplinkperformance/bitbucket-mcp-server

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "bitbucket": {
      "command": "npx",
      "args": [
        "-y",
        "@droplinkperformance/bitbucket-mcp-server"
      ],
      "env": {
        "BITBUCKET_ACCESS_TOKEN": "your-value",
        "BITBUCKET_EMAIL": "your-value",
        "BITBUCKET_DEFAULT_WORKSPACE": "your-value",
        "LLM_PROVIDER": "your-value",
        "OPENAI_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "bitbucket": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@droplinkperformance/bitbucket-mcp-server"
      ],
      "env": {
        "BITBUCKET_ACCESS_TOKEN": "your-value",
        "BITBUCKET_EMAIL": "your-value",
        "BITBUCKET_DEFAULT_WORKSPACE": "your-value",
        "LLM_PROVIDER": "your-value",
        "OPENAI_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

BITBUCKET_ACCESS_TOKEN secret required env
Bitbucket API token (ATATT), app password, or OAuth access token
BITBUCKET_EMAIL required env
Atlassian account email (required with API tokens)
BITBUCKET_DEFAULT_WORKSPACE env
Default Bitbucket workspace when a tool omits workspace
LLM_PROVIDER env
LLM backend for analyze_pull_request (openai, anthropic, gemini, bedrock)
OPENAI_API_KEY secret env
OpenAI API key when LLM_PROVIDER is openai

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account droplinkperformance, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32558 servers in this category
Published to the registry more recently than 30% of the other 32558 servers in this category
Basic checks equal to or better than 100% of the other 32558 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Bitbucket MCP Server safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: BITBUCKET_ACCESS_TOKEN, BITBUCKET_EMAIL, OPENAI_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.2.0) reached the registry 2 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, FactLot

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

FactLot

by 9mp96ygnbk-alt

Cited CRE facts and deterministic calculators for agents: rent, CAM, debt sizing, IRR, parcel IDs.

Computer or cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

@droplinkperformance/bitbucket-mcp-server

Provider-agnostic, AI-review-first Model Context Protocol (MCP) server for Bitbucket Cloud.

The primary value of this server is AI-powered code review and pull request analysis, not CRUD against the Bitbucket API. Every major dependency (SCM access, cache, token storage, rate limiting, LLM, events) is hidden behind a provider-agnostic interface so the same business logic can later target GitHub / GitLab / Azure DevOps and OpenAI / Anthropic / Gemini / Bedrock without changes to use-cases, agents, or domain contracts.

Status: Phase 1. See Roadmap.

Features (Phase 1)

Dual transports: stdio (Cursor / Claude Desktop) and Streamable HTTP (Node http, for remote/production).
Auto-discovered tools via a ToolRegistry — no manual registration.
Explicit `BitbucketContext` (workspace + optional repository) on every tool — multi-workspace ready.
Resilient BitbucketClient: auth injection, auto-pagination, retry/backoff, rate-limit handling, caching, secret masking.
Two auth strategies: OAuth 2.0 (Authorization Code, with rotating refresh-token persistence) and Bearer token.
AI code review (analyze_pull_request) backed by a CodeReviewAgent that chunks large PRs and returns a standard ReviewResult.
Pluggable LLM provider (OpenAI / Anthropic / Gemini / Bedrock), cache (memory / Redis), and token store (file / memory / Redis).

Tools

Tool	Description
`get_current_user`	Authenticated user.
`list_pull_requests`	List PRs (filter by state/query).
`get_pull_request`	Fetch a PR by id.
`create_pull_request`	Open a PR.
`update_pull_request`	Edit an open PR title and/or description.
`get_pull_request_diff`	Raw unified diff.
`get_pull_request_files`	Changed files + line stats.
`get_pull_request_comments`	PR comments.
`comment_pull_request`	Add a (optionally inline) comment.
`analyze_pull_request`	AI review returning a standard `ReviewResult`.

All tool inputs accept workspace (optional if BITBUCKET_DEFAULT_WORKSPACE is set) and, where applicable, repository.

Architecture

src/

index.ts entry: chooses transport container.ts composition root (the only place wiring concretes) mcp/ McpServer + ToolRegistry (auto-discovery) + transports tools/ thin MCP adapters (*.tool.ts) -> call exactly one use-case application/ use-cases (CQRS-ish: command|query) with Input/Output DTOs agents/ autonomous workflows implementing Agent domain/ provider-agnostic types, repository contracts, ReviewResult repositories/bitbucket/ Bitbucket implementations of the contracts clients/bitbucket/ resilient REST client auth/ AuthProvider (+ token/oauth) and TokenStore implementations cache/ CacheProvider (+ memory/redis) ratelimit/ RateLimitStrategy (+ bitbucket) llm/ LlmProvider (+ openai/anthropic/gemini/bedrock) events/ EventBus (+ in-memory) services/ reusable services (masking, chunking) telemetry/ OpenTelemetry bootstrap + metrics infrastructure/ config, logger, http, attachments shared/ errors, result envelope, http-status, BitbucketContext

Flow: tool -> use-case -> (agent | repository contract) -> repositories/bitbucket -> BitbucketClient. Agents may also use the LlmProvider and EventBus. Tools never contain business logic.

Requirements

Node.js 23+

Install

Published as @droplinkperformance/bitbucket-mcp-server.

npx -y @droplinkperformance/bitbucket-mcp-server

From source:

npm install

npm run build

Release

Merges to main run .github/workflows/release.yml: tests, build, then semantic-release. Version and npm publish happen only when the merge includes Conventional Commits:

Commit	Bump
`fix:`	patch
`feat:`	minor
`BREAKING CHANGE` / `feat!:`	major

Other messages skip publish. The GitHub secret NPM_TOKEN (npm Automation token for the droplinkperformance org) is required.

After a successful npm release, the same workflow waits until that version is visible on the npm registry, then publishes metadata to the MCP Registry as io.github.droplinkperformance/bitbucket-mcp-server (OIDC, no extra secret). To republish MCP metadata for the current package.json version without cutting a new release, run the workflow manually with Publish mcp only. github.com/mcp syncs from that registry; if the server does not appear, email partnerships@github.com.

To stay on 0.x for the first release, tag the current commit (git tag v0.1.0 && git push origin v0.1.0) before the first conventional merge; otherwise semantic-release starts at 1.0.0.

Configuration

Copy .env.example to .env and fill in values. Load it with Node's built-in flag:

node --env-file=.env dist/index.js

Key variables:

Variable	Default	Notes
`MCP_TRANSPORT`	`stdio`	`stdio` or `http`.
`HTTP_HOST` / `HTTP_PORT`	`0.0.0.0` / `3000`	HTTP transport bind.
`BITBUCKET_DEFAULT_WORKSPACE`	–	Fallback when a tool omits `workspace`.
`BITBUCKET_ACCESS_TOKEN`	–	API token (ATATT…), app password, or OAuth access token
`BITBUCKET_EMAIL`	–	Required with API tokens (ATATT…) — your Atlassian account email
`BITBUCKET_CLIENT_ID` / `BITBUCKET_CLIENT_SECRET`	–	Required for OAuth (when no access token).
`BITBUCKET_REFRESH_TOKEN`	–	Optional seed for headless OAuth.
`TOKEN_STORE`	`file`	`file` \	`memory` \	`redis`.
`CACHE_PROVIDER`	`memory`	`memory` \	`redis`.
`LLM_PROVIDER`	`openai`	`openai` \	`anthropic` \	`gemini` \	`bedrock`.
`MAX_FILES_PER_CHUNK` / `MAX_DIFF_LINES_PER_CHUNK`	`50` / `5000`	Large-PR chunking thresholds.
`OTEL_ENABLED`	`false`	No-op metrics unless enabled.

Authentication

Bearer (OAuth access token): set BITBUCKET_ACCESS_TOKEN only (non-ATATT tokens).

API token (recommended, ATATT…): set BITBUCKET_ACCESS_TOKEN and BITBUCKET_EMAIL (your Atlassian account email from Bitbucket → Personal settings → Email aliases). API tokens use HTTP Basic auth, not Bearer.

App password (legacy, until June 2026): set BITBUCKET_ACCESS_TOKEN and BITBUCKET_USERNAME (your Bitbucket username).

OAuth 2.0 (Authorization Code): set BITBUCKET_CLIENT_ID / BITBUCKET_CLIENT_SECRET. Tokens are persisted by the configured TOKEN_STORE; Bitbucket rotates refresh tokens, and the server persists the new one on every refresh. For headless boot, provide a previously obtained BITBUCKET_REFRESH_TOKEN.

Bitbucket OAuth endpoints used: authorize https://bitbucket.org/site/oauth2/authorize, token https://bitbucket.org/site/oauth2/access_token. The authorize URL can be built from OAuthProvider.buildAuthorizeUrl() and the returned ?code= exchanged via OAuthProvider.loginWithCode(code).

LLM provider

Set LLM_PROVIDER and the matching key:

LLM_PROVIDER=openai      # OPENAI_API_KEY

LLM_PROVIDER=anthropic # ANTHROPIC_API_KEY LLM_PROVIDER=gemini # GEMINI_API_KEY LLM_PROVIDER=bedrock # AWS creds + BEDROCK_MODEL_ID (needs @aws-sdk/client-bedrock-runtime)

ioredis (Redis providers) and @aws-sdk/client-bedrock-runtime (Bedrock) are optional and loaded lazily — only needed when selected.

Running

stdio

MCP_TRANSPORT=stdio node --env-file=.env dist/index.js

Streamable HTTP

MCP_TRANSPORT=http HTTP_PORT=3000 node --env-file=.env dist/index.js

health: GET http://localhost:3000/health

endpoint: POST http://localhost:3000/mcp

MCP Inspector

npx @modelcontextprotocol/inspector node dist/index.js

Cursor

~/.cursor/mcp.json (or project .cursor/mcp.json):

"mcpServers": { "bitbucket": { "command": "npx", "args": ["-y", "@droplinkperformance/bitbucket-mcp-server"], "env": { "MCP_TRANSPORT": "stdio", "BITBUCKET_ACCESS_TOKEN": "ATATT-your-api-token", "BITBUCKET_EMAIL": "you@company.com", "BITBUCKET_DEFAULT_WORKSPACE": "your-workspace", "LLM_PROVIDER": "openai", "OPENAI_API_KEY": "sk-..." } } } }

Claude Desktop

claude_desktop_config.json:

"mcpServers": { "bitbucket": { "command": "npx", "args": ["-y", "@droplinkperformance/bitbucket-mcp-server"], "env": { "BITBUCKET_ACCESS_TOKEN": "your-token", "BITBUCKET_DEFAULT_WORKSPACE": "your-workspace", "LLM_PROVIDER": "anthropic", "ANTHROPIC_API_KEY": "sk-ant-..." } } } }

Development

npm run dev          # tsx watch (stdio)

npm run typecheck npm run lint npm test npm run test:coverage

Roadmap

Phase 1 (this release): auth, abstractions, BitbucketClient, tool auto-discovery, PR tools, analyze_pull_request.
Phase 2: Pipelines + full-text paginated logs, pipeline-investigator agent, auto_review_pull_request (dry-run / publish inline comments).
Phase 3: Remaining CRUD — repositories, commits, branches, tags, issues, workspaces, members, search.
Phase 4: analyze_dotnet_pull_request (dotnet-review agent), advanced agents, automation workflows.
Phase 5: Docker, Compose, Helm, production deploy guide.

License

MIT

Bitbucket MCP Server

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

FactLot

README from the maker

@droplinkperformance/bitbucket-mcp-server

Features (Phase 1)

Tools

Architecture

Requirements

Install

Release

Configuration

Authentication

LLM provider

Running

stdio

Streamable HTTP

health: GET http://localhost:3000/health

endpoint: POST http://localhost:3000/mcp

MCP Inspector

Cursor

Claude Desktop

Development

Roadmap

License