A
licenseA
qualityB
maintenanceEnables MCP clients to browse and interact with Bitbucket Cloud, exposing workspace, repository, branch, and pull request operations as tools.
18
9 npm
MIT
Bitbucket MCP Server
by chzkyy
Related Servers
Alternatives to Bitbucket MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that provides tools for interacting with the Bitbucket API, supporting both Bitbucket Cloud and Bitbucket Server, enabling pull request, branch, file, code review, and search operations.198,929 npmMIT
- FlicenseBqualityBmaintenanceEnables 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-
- AlicenseBqualityBmaintenanceA read-only MCP server that provides secure access to Bitbucket repositories, pull requests, issues, and more.38195 npm3MIT
- AlicenseBqualityCmaintenanceMCP server for Bitbucket Server integration, enabling project, repository, pull request, source code, branch, and code review operations via the Bitbucket Server APIs.2729 npmMIT
- AlicenseNot gradedqualityDmaintenanceA read-only MCP server for the Bitbucket Cloud REST API v2.0 that enables AI assistants to browse workspaces, repositories, and review pull requests.75 npmISC
TDQS
A3.8/5.0
Scored across 12 tools
Disambiguation5/5
Each tool targets a distinct resource and action: workspaces, repositories, branches, commits, directories, file contents, code search, PRs, README, and commit diffs are all clearly separated. Even get_commit and get_commit_diff differ by returning commit metadata versus diff output.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern, with list_ for collections and get_ for single items. The singular/plural differences (list_repositories vs get_repository) are logical and match the resource granularity.
Tool Count5/5
With 12 tools covering read-only Bitbucket operations, the count fits well within the ideal 3-15 range. Each tool serves a distinct purpose and contributes to the overall browsing and searching workflow.
Completeness4/5
The tool set provides solid read-only coverage for exploring workspaces, repositories, branches, commits, file contents, code search, and commit diffs. A notable gap is the lack of a get_pull_request detail endpoint (only list exists) and no PR diff retrieval, but these are minor for a browsing-focused server.
Maintenance
ActivitySlowing
ResponsivenessNo issues