Bitbucket Cloud MCP Server
Related Servers
Alternatives to Bitbucket Cloud MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Bitbucket Cloud REST API 2.0, supporting pull requests, pipelines, logs, and repository cloning through MCP tools.36 npmMIT
- AlicenseBqualityBmaintenanceEnables AI assistants to interact with Bitbucket Cloud and self-hosted instances for pull request reviews, code search, repository operations, and managing PR comments and approvals.19GPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables interaction with Bitbucket Server/Data Center (Stash) for project and repository discovery, pull request management, code review, and code search.14 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables users to securely access and manage Bitbucket Data Center projects, repositories, pull requests, branches, commits, and build statuses through natural language, using per-user OAuth 2.0 authentication and granular read/write permissions.MIT
- AlicenseBqualityBmaintenanceEnables Bitbucket Cloud code review and PR workflows from Claude Code, covering repos, pull requests, commits, branches, file browsing, code search, and workspace/user discovery.2616 npmMIT
- FlicenseBqualityCmaintenanceEnables interaction with a Bitbucket Server/Data Center instance, exposing its REST v1.0 API as MCP tools to manage projects, repositories, branches, pull requests, comments, diffs, commits, files, search, and build status.41-
TDQS
Scored across 34 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the Bitbucket Cloud domain. For example, 'get_pull_request' retrieves details while 'approve_pull_request' performs an action, and tools like 'list_pr_comments' vs 'add_pr_comment' handle different aspects of PR comments without overlap.
All tools follow a consistent verb_noun pattern with snake_case throughout, such as 'create_branch', 'list_issues', 'update_pull_request'. There are no deviations in naming conventions, making the set highly predictable and readable.
With 34 tools, the count is borderline high for a single server, potentially feeling heavy and overwhelming for agents. While it covers many Bitbucket Cloud operations, a more modular approach might improve usability without sacrificing functionality.
The tool surface provides comprehensive CRUD and lifecycle coverage for repositories, branches, commits, issues, pull requests, pipelines, and code search. It includes all essential operations like create, get, list, update, delete, and specific actions such as merge, approve, and trigger, with no obvious gaps for the domain.