MCP Bitbucket Python
Related Servers
Alternatives to MCP Bitbucket Python
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.5922 npm3MIT
- AlicenseAqualityDmaintenanceAn MCP server for BitBucket Cloud operations that enables AI agents to manage repositories, branches, pull requests, and search code.32MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude and other AI agents to manage Bitbucket Cloud repositories, pull requests, branches, tags, commits, diffs, files, and pipelines through a secure local MCP server with read and write tools.MIT
- FlicenseNot gradedqualityFmaintenanceThis MCP server enables AI agents to create Pull Requests in a self-hosted Bitbucket Server instance.-
- AlicenseBqualityDmaintenanceMCP server for Bitbucket Cloud that enables AI agents to manage repositories, branches, pull requests, and deployments via typed tools.1733 npmISC
- 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
TDQS
Scored across 10 tools
Every tool has a clearly distinct purpose targeting specific Bitbucket resources and actions, with no overlap or ambiguity. For example, bb_create_branch, bb_create_issue, and bb_create_pull_request each handle different creation operations, while bb_read_file and bb_write_file are distinct file operations.
All tools follow a consistent 'bb_verb_noun' pattern throughout, using snake_case and starting with 'bb_' as a prefix. This predictable naming convention makes it easy to understand each tool's function at a glance, with no deviations or mixed styles.
With 10 tools, the server is well-scoped for Bitbucket operations, covering repository, branch, issue, pull request, and file management. Each tool earns its place by addressing a core functionality without being overly broad or sparse, fitting typical server tool counts of 3-15.
The tool set provides strong CRUD/lifecycle coverage for Bitbucket's key resources, including create/delete for repositories, issues, and files, and create for branches and pull requests. A minor gap exists in update operations (e.g., updating issues or pull requests), but agents can work around this with create/delete or other methods.