Official description7 sourcesMCP servers8d ago
daniloneto/bitbucket-mcp
Bitbucket Cloud pull-requ
View on GitHub ↗Direct link · no redirect page
Config template (adjust for your client)
claude mcp add bitbucket-mcp -- npx -y bitbucket-mcp
A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
- Star count
- 0 ★ · daniloneto/bitbucket-mcp · read from the repository page · (checked 2026-10-16 20:00:20)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
- Score
- score 703 · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
daniloneto/bitbucket-mcp；first catalogued 2026-10-09；last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.Third-party quality signals
bitbucket-mcp
以下摘录自该仓库的 README（片段） · 在 GitHub 读完整 README →
**English** · Português (BR)
MCP server for **Bitbucket Cloud**, focused on the *first pass* of pull-request review. **stdio** transport, for use with **Claude Code** or Claude Desktop.
Why an API token (and not an app password)
Bitbucket Cloud app passwords have been in brownout since 2026-06-09 and are **removed on 2026-07-28**. This server uses an **API token**, and the HTTP Basic pair is email:token — the Bitbucket REST API requires the **Atlassian account email**, not the username. Using the username results in a silent 401.
1. Create the API token
1. Bitbucket top bar → **Settings → Atlassian account settings → Security**.
2. **Create and manage API tokens → Create API token with scopes**.
3. Name it, set an expiry, and select **Bitbucket** as the app.
4. Minimum scopes for PR review:
- read:repository:bitbucket (read repositories, diffs, files)
- read:pullrequest:bitbucket (read PRs and comments)
- write:pullrequest:bitbucket (comment, approve, request changes)
5. Copy the token (**shown only once**).
2. Install and build
This generates dist/index.js (the server binary).
3. Configure in Claude Code
Add this to the project's .mcp.json (or to your global Claude Code config):
Alternative, via the CLI:
BITBUCKET_WORKSPACE is optional; if omitted, each tool must be given workspace explicitly.
Tools
Read (no side effects):
| Tool | Purpose |
|------|---------|
| list_repositories | Repositories in the workspace |
| list_pull_requests | PRs by state (OPEN/MERGED/DECLINED/SUPERSEDED) |
| get_pull_request | PR metadata (description, branches, reviewers, approvals) |
| get_pull_request_diff | Unified diff — the basis for the review |
| get_pull_request_comments | Existing comments (general and inline) |
| get_pull_request_commits | PR commits |
| list_directory | Lists the repo file tree at a commit/branch (explore the project) |
| get_file | Contents of a file (default branch if commit is omitted) |
Write (**mutate state in Bitbucket**):
| Tool | Purpose |
|------|---------|
| add_pull_request_comment | Comment on the PR; path + line together = inline |
| approve_pull_request | Approve the PR |
| request_changes_pull_request | Mark "request changes" |
MCP server for **Bitbucket Cloud**, focused on the *first pass* of pull-request review. **stdio** transport, for use with **Claude Code** or Claude Desktop.
Why an API token (and not an app password)
Bitbucket Cloud app passwords have been in brownout since 2026-06-09 and are **removed on 2026-07-28**. This server uses an **API token**, and the HTTP Basic pair is email:token — the Bitbucket REST API requires the **Atlassian account email**, not the username. Using the username results in a silent 401.
1. Create the API token
1. Bitbucket top bar → **Settings → Atlassian account settings → Security**.
2. **Create and manage API tokens → Create API token with scopes**.
3. Name it, set an expiry, and select **Bitbucket** as the app.
4. Minimum scopes for PR review:
- read:repository:bitbucket (read repositories, diffs, files)
- read:pullrequest:bitbucket (read PRs and comments)
- write:pullrequest:bitbucket (comment, approve, request changes)
5. Copy the token (**shown only once**).
2. Install and build
This generates dist/index.js (the server binary).
3. Configure in Claude Code
Add this to the project's .mcp.json (or to your global Claude Code config):
Alternative, via the CLI:
BITBUCKET_WORKSPACE is optional; if omitted, each tool must be given workspace explicitly.
Tools
Read (no side effects):
| Tool | Purpose |
|------|---------|
| list_repositories | Repositories in the workspace |
| list_pull_requests | PRs by state (OPEN/MERGED/DECLINED/SUPERSEDED) |
| get_pull_request | PR metadata (description, branches, reviewers, approvals) |
| get_pull_request_diff | Unified diff — the basis for the review |
| get_pull_request_comments | Existing comments (general and inline) |
| get_pull_request_commits | PR commits |
| list_directory | Lists the repo file tree at a commit/branch (explore the project) |
| get_file | Contents of a file (default branch if commit is omitted) |
Write (**mutate state in Bitbucket**):
| Tool | Purpose |
|------|---------|
| add_pull_request_comment | Comment on the PR; path + line together = inline |
| approve_pull_request | Approve the PR |
| request_changes_pull_request | Mark "request changes" |
- Source
- awesome · https://github.com/daniloneto/bitbucket-mcp
- Browse by field
- MCP servers
- added
- yesterday
More in MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.