Compared · bitbucket
6 Bitbucket MCP servers. Which one to use.
Every Bitbucket server we index, with whether its source is still reachable and whether we hold a screening verdict. None currently carry a source-liveness flag.
Scope: 6 servers, mostly mirrored from the MCP registry as of 2026-08-13. Most servers whose authors never published to the registry are absent, so treat this as close to the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Bitbucket MCP Server | io.github.lawp09 | no flag | REVIEW | 90 | pypi bitbucket-mcp-py |
| Bitbucket MCP | io.github.FabianSchurig | no flag | REVIEW | 85 | docker ghcr.io/fabianschurig/bitbucket-mcp:0.18.5 |
| com.mcparmory/bitbucket | com.mcparmory | no flag | REVIEW | 80 | pypi mcparmory-bitbucket |
| io.github.MrRefactoring/atlassian-dc-mcp-bitbucket | io.github.MrRefactoring | no flag | REVIEW | 80 | npm bitbucket-datacenter-mcp |
| io.github.b1ff/atlassian-dc-mcp-bitbucket | io.github.b1ff | no flag | REVIEW | 80 | npm @atlassian-dc-mcp/bitbucket |
| Bitbucket MCP | io.github.MatanYemini | no flag | REVIEW | 62 | npm bitbucket-mcp |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.