A
licenseNot graded
qualityA
maintenanceEnables AI assistants to interact with Bitbucket Cloud repositories, allowing users to manage pull requests, comments, tasks, and branches through natural language commands.
3,208 npm
1
MIT
bitbucket-mcp
by lawp09
Related Servers
Alternatives to bitbucket-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to programmatically manage Bitbucket Cloud resources, including pull requests, repositories, and branches, automating code review workflows.11 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
- AlicenseBqualityDmaintenanceEnables AI assistants to read Bitbucket Cloud pull requests and diffs through natural conversation.221 npmMIT
- AlicenseNot gradedqualityDmaintenanceConnects AI assistants to Bitbucket Server/Data Center for reviewing pull requests, managing repositories, searching users, and more.149 npm4MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to manage Bitbucket Cloud repositories, pull requests, branches, commits, pipelines, issues, and webhooks through the Model Context Protocol.81,155 npmMIT
TDQS
B3.3/5.0
Scored across 74 tools
Disambiguation4/5
Most tools target a clear resource+action pair, and plural/singular naming separates collections from single items. The main ambiguities are create_draft_pull_request duplicating create_pull_request's draft parameter, and submit_pull_request_batch_review overlapping with approve/request_changes/add_comment, but detailed descriptions mostly resolve these.
Naming Consistency3/5
Names are consistently snake_case with verb-first ordering, but the list/get convention is inconsistent: list_repositories and list_issues coexist with get_pull_requests, get_issue_comments, and get_repository_tags for collections. There is also mixed add_ vs create_ for comments/tasks and the awkward unrequest_changes_pull_request.
Tool Count1/5
74 tools is an extreme surface for a single MCP server, exceeding the 50+ threshold. Many tools are read-only admin/list operations that add bulk without earning interaction value for common workflows.
Completeness2/5
The PR subdomain is well covered with lifecycle, comments, tasks, diffs, and review workflows, but the broader Bitbucket domain has major gaps: no repository create/delete, no branch or file write operations, no issue deletion, and pipeline variables/schedules, deployments, branch restrictions, and permissions are read-only. These gaps will cause agent failures when a task requires management actions beyond pull request review.
Maintenance
ActivityMaintained
ResponsivenessUnresponsive