A side-by-side look at the Atlassian Dc MCP Bitbucket 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 Atlassian Dc MCP Bitbucket 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.
BITBUCKET_HOST, BITBUCKET_API_TOKEN, BITBUCKET_API_BASE_PATH.BITBUCKET_EMAIL, BITBUCKET_API_TOKEN, BITBUCKET_WORKSPACE.list_repositories, list_pull_requests, get_pull_request.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 43/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_HOSTBITBUCKET_API_TOKENBITBUCKET_API_BASE_PATH | BITBUCKET_EMAILBITBUCKET_API_TOKENBITBUCKET_WORKSPACE |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 11 |
| Full listing | View Atlassian Dc MCP Bitbucket | View Bitbucket MCP |
No tool names declared yet. Check the project README from the listing page.
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"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.
{
"mcpServers": {
"atlassian-dc-mcp-bitbucket": {
"command": "npx",
"args": [
"-y",
"jira-datacenter-mcp"
],
"env": {
"BITBUCKET_HOST": "YOUR_BITBUCKET_HOST_HERE",
"BITBUCKET_API_TOKEN": "YOUR_BITBUCKET_API_TOKEN_HERE",
"BITBUCKET_API_BASE_PATH": "YOUR_BITBUCKET_API_BASE_PATH_HERE"
}
}
}
}
No confirmed install command for Bitbucket MCP yet — follow the setup steps linked from its listing page rather than a guessed package name.