Bitbucket MCP Server vs Bitbucket MCP
A side-by-side look at the Bitbucket MCP Server and Bitbucket MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bitbucket MCP Server for version control work as a local process; choose Bitbucket MCP for version control. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Bitbucket MCP Server when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
BITBUCKET_USERNAME, BITBUCKET_TOKEN, BITBUCKET_WORKSPACE, BITBUCKET_TOOLS_CONFIG.
Choose Bitbucket MCP when
- You need dedicated capabilities in the Version Control domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
BITBUCKET_EMAIL, BITBUCKET_API_TOKEN, BITBUCKET_WORKSPACE. - You want tools like
list_repositories, list_pull_requests, get_pull_request.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 41/100 · Fair | 48/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | BITBUCKET_USERNAMEBITBUCKET_TOKENBITBUCKET_WORKSPACEBITBUCKET_TOOLS_CONFIG | BITBUCKET_EMAILBITBUCKET_API_TOKENBITBUCKET_WORKSPACE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 11 |
| Full listing | View Bitbucket MCP Server | View Bitbucket MCP |
Tools & capabilities
Bitbucket MCP Server tools
No tool names declared yet. Check the project README from the listing page.
Bitbucket MCP tools 11
list_repositoriesRepositories in the workspacelist_pull_requestsPRs by state (OPEN/MERGED/DECLINED/SUPERSEDED)get_pull_requestPR metadata (description, branches, reviewers, approvals)get_pull_request_diffUnified diff — the basis for the reviewget_pull_request_commentsExisting comments (general and inline)get_pull_request_commitsPR commitslist_directoryLists the repo file tree at a commit/branch (explore the project)get_fileContents of a file (default branch if `commit` is omitted)add_pull_request_commentComment on the PR; `path` + `line` together = inlineapprove_pull_requestApprove the PRrequest_changes_pull_requestMark "request changes"
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Bitbucket MCP Server
{
"mcpServers": {
"bitbucket-mcp-server-2": {
"command": "uvx",
"args": [
"--from",
"bitbucket-mcp-py",
"bitbucket-mcp"
],
"env": {
"BITBUCKET_USERNAME": "YOUR_BITBUCKET_USERNAME_HERE",
"BITBUCKET_TOKEN": "YOUR_BITBUCKET_TOKEN_HERE",
"BITBUCKET_WORKSPACE": "YOUR_BITBUCKET_WORKSPACE_HERE",
"BITBUCKET_TOOLS_CONFIG": "YOUR_BITBUCKET_TOOLS_CONFIG_HERE"
}
}
}
}
Bitbucket MCP
No confirmed install command for Bitbucket MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Bitbucket MCP Server is categorized under Version Control and uses a local stdio subprocess. Bitbucket MCP belongs to Version Control and uses an install path we have not confirmed yet. Pick Bitbucket MCP Server for version control work and Bitbucket MCP for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Bitbucket MCP has no confirmed install command yet — follow its own setup instructions.
Bitbucket MCP Server has no declared pricing — check the project's own site. Bitbucket MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add bitbucket-mcp-server-2 and daniloneto-bitbucket-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bitbucket MCP Server has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 3 GitHub stars. Bitbucket MCP has 48/100 (Fair) with 4 views, 0 installs and 0 GitHub stars.