@jestay/bitbucket-mcp
Related Servers
Alternatives to @jestay/bitbucket-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceMCP server for Bitbucket Cloud that enables reviewing, managing, and merging pull requests, assigning reviewers by name, reading files at a ref, and inspecting pipeline status from any MCP client.14MIT
- AlicenseAqualityDmaintenanceMCP server for Bitbucket Cloud, focused on pull-request review workflows115,300 npmMIT
- AlicenseAqualityBmaintenanceAn MCP server for reviewing Bitbucket Cloud pull requests, allowing clients to read PRs, tickets, and comments and leave review comments without leaving the editor.75,300 npmMIT
- FlicenseAqualityCmaintenanceAn MCP server for Bitbucket Cloud that enables reading and managing pull requests, comments, and descriptions via MCP clients.17-
- FlicenseCqualityCmaintenanceAn MCP server for Bitbucket Cloud, covering pull requests, pull request comments, and pipelines.26-
- AlicenseBqualityBmaintenanceMCP server for Bitbucket Server integration, enabling project, repository, pull request, source code, branch, and code review operations via the Bitbucket Server APIs.2717 npmMIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: listing PRs, getting PR metadata, getting the diff, reading file content, listing comments, and posting comments. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern using snake_case, such as list_pull_requests, get_pull_request_diff, and create_pull_request_comment. The naming is uniform and predictable.
With exactly 6 tools, the server is well-scoped for a pull request review workflow. Each tool serves a necessary function without redundancy or bloat.
The tool set covers the full review loop: discover PRs, inspect details and diffs, view file contents for context, check existing comments, and post new feedback. No critical gaps are apparent for the intended purpose.