A
licenseC
qualityB
maintenanceMCP server for integrating with Bitbucket Cloud and Server APIs, enabling AI assistants to interact with repositories, pull requests, pipelines, and more.
59
44 npm
3
MIT
bitbucket-mcp-server
by mdanelutti
Related Servers
Alternatives to bitbucket-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Bitbucket Cloud, focused on pull-request review workflows114,764 npmMIT
- 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.1747 npmISC
- 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
- AlicenseAqualityBmaintenanceMCP server for code review of Bitbucket Cloud pull requests: list PRs, read diffs, file contents and comments, and post review comments.611 npmISC
TDQS
B3.3/5.0
Scored across 14 tools
Disambiguation4/5
Read tools (list, get, diff, comments, activity) and write tools (create, update, approve, unapprove, request_changes, comment, merge, decline) each target a distinct action on a pull request. Slight potential for confusion between get_pull_request_activity and get_pull_request_comments (activity logs often include comments), and between approve_pull_request and request_changes, but descriptions clarify the boundaries.
Naming Consistency5/5
Every tool follows a consistent snake_case verb_noun pattern (list_pull_requests, get_pull_request_diff, add_pull_request_comment, merge_pull_request). Even the odd-one-out search_workspace_members fits the same convention.
Tool Count5/5
14 tools is well within the ideal range and each maps to a meaningful step in the PR review/merge workflow. No redundant or filler tools are present.
Completeness4/5
The pull request lifecycle is thoroughly covered: discovery, inspection, creation, updates, review states (approve/unapprove/request changes), commenting, and merge/decline. Minor gaps remain around repository/branch discovery (no list_repositories or branch tools), which an agent may need to locate a repo before working with its PRs.
Maintenance
ActivityInactive
ResponsivenessNo issues