bitbucket-review-mcp

An MCP server for interactive Bitbucket Cloud pull-request review with Claude. Claude reads the PR, its diff and the surrounding source code, analyses design/data-flow, proposes per-module test cases and best practices, and — only when you confirm — posts findings back as inline + summary comments.

Tools exposed

Installation

Install from PyPI:

pip install bitbucket-review-mcp

This installs a console command, bitbucket-review-mcp, that runs the MCP server over stdio.

Install from source

git clone https://github.com/fahidnibu/pr_mcp.git
cd pr_mcp
pip install .

Configuration

The server reads credentials from environment variables (or a .env file in the directory it is launched from). Copy .env.example to .env and fill it in:

# Prefer an access token (Bitbucket → Workspace/Repo settings → Access tokens).
# Scopes needed: pullrequest (read) and pullrequest:write (to post comments).
BITBUCKET_ACCESS_TOKEN=

# Fallback auth if you don't use an access token (app passwords are being
# phased out by Atlassian):
BITBUCKET_USERNAME=
BITBUCKET_APP_PASSWORD=

# Optional defaults so you can review by PR id alone:
BITBUCKET_WORKSPACE=
BITBUCKET_REPO_SLUG=

Register with Claude Code

Add the server to your .mcp.json (this repo ships one already):

{
  "mcpServers": {
    "bitbucket": {
      "command": "bitbucket-review-mcp"
    }
  }
}

Restart Claude Code so it picks up .mcp.json, approve the bitbucket server when prompted, and verify with /mcp.

If the bitbucket-review-mcp command isn't on your PATH (e.g. it's installed in a virtualenv), use the interpreter form instead:

{
  "mcpServers": {
    "bitbucket": {
      "command": "python",
      "args": ["-m", "bitbucket_review_mcp.server"]
    }
  }
}

Usage

Just ask Claude, e.g.:

• "Review PR 412"
• "Review PR 88 in repo web-app"
• "List open PRs, then review the newest one"

Claude presents the full review in chat first and always asks before posting anything to Bitbucket.

Development & publishing to PyPI

Build the distribution artifacts (wheel + sdist):

pip install --upgrade build twine
python -m build

This produces dist/*.whl and dist/*.tar.gz. Check and upload them:

twine check dist/*

# Upload to TestPyPI first (recommended):
twine upload --repository testpypi dist/*

# Then the real index:
twine upload dist/*

You'll be prompted for credentials — use a PyPI API token (username __token__, password = the token). Bump version in both pyproject.toml and src/bitbucket_review_mcp/__init__.py before each release; PyPI rejects re-uploads of an existing version.

Note: bitbucket-review-mcp is the distribution name declared in pyproject.toml. If that name is already taken on PyPI, change name in pyproject.toml (the import package bitbucket_review_mcp can stay).

License

MIT