# daniloneto/bitbucket-mcp [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/daniloneto/bitbucket-mcp  
**GitHub Stars:** 0  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/daniloneto-bitbucket-mcp

## Description
MCP server for Bitbucket Cloud focused on pull-request review — read PRs, diffs, comments, commits, files and the repo tree; post inline/general comments, approve, or request changes. Uses Atlassian API tokens (stdio).

## Tools
Capabilities this server exposes over MCP:

- **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)
- **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"

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "bitbucket-mcp": {
    "command": "npx",
    "args": ["-y","daniloneto-bitbucket-mcp"],
    "env": {
      "BITBUCKET_EMAIL": "",
      "BITBUCKET_API_TOKEN": "",
      "BITBUCKET_WORKSPACE": ""
    }
  }
}
```

**Requires environment variables:** `BITBUCKET_EMAIL`, `BITBUCKET_API_TOKEN`, `BITBUCKET_WORKSPACE` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What daniloneto/bitbucket-mcp MCP server does

The daniloneto/bitbucket-mcp MCP server connects an MCP-compatible client to Bitbucket Cloud for pull-request review. It supports both inspection and selected review mutations. An agent can discover repositories, locate pull requests by state, inspect metadata, read the unified diff, review existing discussion, examine commits, and browse repository files.

The write operations are limited to pull-request review actions: adding a general or inline comment, approving a pull request, and marking it as requiring changes. For an inline comment, the comment request includes both a file path and line. The server is intended for a first review pass rather than broad Bitbucket administration.

## How it works

The server uses the stdio transport, so the MCP client starts a local Node process and communicates with it through standard input and output. It calls the Bitbucket Cloud REST API using HTTP Basic authentication with the Atlassian account email as the username and the API token as the password. The README specifically warns that the Bitbucket username is not the correct value for this authentication pair.

A workspace can be supplied through configuration as a default. If no default is configured, each tool call must provide a workspace explicitly. Read tools do not mutate Bitbucket state. Commenting, approving, and requesting changes do mutate pull-request state and require the corresponding write scope.

## Setup and configuration

Clone or obtain the repository, then run `npm install` followed by `npm run build`. The build creates `dist/index.js`, which is the local server entry point. Configure the MCP client to run it with Node and pass the required environment variables:

- `BITBUCKET_EMAIL`: the Atlassian account email used for authentication.
- `BITBUCKET_API_TOKEN`: the Bitbucket API token.
- `BITBUCKET_WORKSPACE`: an optional default workspace.

The token is created in Atlassian account security settings with Bitbucket selected as the application. The documented minimum review scopes are repository read, pull-request read, and pull-request write. A read-only token is suitable when an agent should suggest findings without being able to comment or change approval status.

The daniloneto/bitbucket-mcp MCP server can be added to a project or global Claude Code configuration, and the README also identifies Claude Desktop as a supported use environment. The example configuration uses an absolute path to the built `dist/index.js` file.

## Tools and capabilities

Read-only capabilities include:

- Listing repositories in a workspace.
- Listing pull requests filtered by open, merged, declined, or superseded state.
- Reading pull-request descriptions, branches, reviewers, and approvals.
- Retrieving unified diffs, existing general and inline comments, and commits.
- Listing a repository tree at a branch or commit.
- Reading file contents, using the default branch when no commit is specified.

State-changing capabilities include adding general or inline comments, approving a pull request, and requesting changes.

## Limitations and notes

The server targets Bitbucket Cloud, not a general Bitbucket administration surface. Its documented focus is first-pass pull-request review. API-token permissions determine which operations succeed, so write tools should not be treated as harmless suggestions when the configured token has write access.

Keep the token in environment variables or a secret manager and do not commit it. The token grants read and write access to pull requests in the permitted workspace. The daniloneto/bitbucket-mcp MCP server is licensed under MIT.

_Full upstream README: https://allmcps.com/mcp/daniloneto-bitbucket-mcp/readme_