An MCP server for interactive Bitbucket Cloud pull-request review with Claude.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"bitbucket-review-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# bitbucket-review-mcp An [MCP](https://modelcontextprotocol.io) 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 | Tool | Purpose | | --- | --- | | `list_open_prs` | List open pull requests. | | `get_pr` | PR metadata: title, description, branches, commit hashes. | | `get_pr_diff` | The raw unified diff for a PR. | | `get_pr_files` | Changed files with per-file added/removed line counts. | | `get_file_content` | Read a file's full contents at a commit/branch. | | `post_inline_comment` | Post an inline comment on a line in the diff. | | `post_summary_comment` | Post a top-level summary comment on the PR. | ## Installation Install from PyPI: ```bash pip install bitbucket-review-mcp ``` This installs a console command, `bitbucket-review-mcp`, that runs the MCP server over stdio. ### Install from source ```bash 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: ```bash # 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): ```json { "mcpServers": { "bitbucket": { "command": "bitbucket-review-mcp" } } } ``` Restart …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.