A
licenseA
qualityD
maintenanceAn MCP server for BitBucket Cloud operations that enables AI agents to manage repositories, branches, pull requests, and search code.
32
MIT
bitbucket-mcp-server
by fnops
Related Servers
Alternatives to bitbucket-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceMCP server for integrating with Bitbucket Cloud and Server APIs, enabling AI assistants to interact with repositories, pull requests, pipelines, and more.5919 npm3MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Bitbucket Cloud that exposes 35 tools covering repositories, pull requests, branching models, and pipelines, enabling AI clients to automate Bitbucket workflows.3MIT
- FlicenseNot gradedqualityCmaintenanceThis MCP server enables AI agents to create Pull Requests in a self-hosted Bitbucket Server instance.-
- FlicenseNot gradedqualityCmaintenanceMCP server for Bitbucket Data Center that enables PR creation, review comment management, and rebasing workflows through natural language commands.-
- AlicenseBqualityDmaintenanceMCP server for Bitbucket Cloud that exposes Pull Request operations as tools for Claude and other MCP clients.1424 npmISC
TDQS
B3.4/5.0
Scored across 17 tools
Disambiguation5/5
Every tool targets a distinct resource and action. The list tools (tags, repositories, projects, branches, PRs, deployments) are clearly separated by resource, and PR tools cover distinct lifecycle actions (create, get, approve, decline, merge, comments). No two tools appear to overlap.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case (list_*, get_*, create_*, clone_, approve_, decline_, merge_, add_). There is no mixing of casing or verb style, making the set predictable.
Tool Count4/5
17 tools is slightly above the ideal 3-15 range, but the breadth is justified by covering repository browsing, branches, pull requests, and deployments. The count is reasonable and not bloated; every tool serves a distinct purpose.
Completeness3/5
The pull request lifecycle is well-covered (create, list, get, approve, decline, merge, comments), and browsing tools are solid. However, there are no repository creation/update/delete operations, and no update endpoint for pull requests or branch deletion. These are notable gaps for a Bitbucket server.
Maintenance
ActivityInactive
ResponsivenessNo issues