mcp-server-bitbucket
Related Servers
Alternatives to mcp-server-bitbucket
No user-submitted related servers found.
Related Servers
- AlicenseBqualityCmaintenanceAn MCP server for Atlassian Bitbucket Server / Data Center, providing 66 tools for managing projects, repositories, branches, files, commits, pull requests, and code search with opt-in deletion operations.57137 PyPI1MIT
- 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.1911,347 npmMIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for Bitbucket integration, providing 27 tools to manage repositories, pull requests, branches, commits, issues, and workspaces.MIT
- 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
- AlicenseBqualityCmaintenanceMCP server for the Bitbucket Cloud REST API v2.0, providing 32 tools across 5 toolsets for repository management, pull requests, issues, pipelines, and more with safety controls and LLM-optimized output.3313 npm2MIT
- AlicenseBqualityBmaintenanceMCP server for Bitbucket Server integration, enabling project, repository, pull request, source code, branch, and code review operations via the Bitbucket Server APIs.27768 npmMIT
TDQS
Scored across 62 tools
Most tools target clearly distinct resources and actions (repositories, PRs, pipelines, permissions, webhooks, tags, branches). A few adjacent commit/file-history tools and pipeline status/log tools require reading descriptions carefully, but overall boundaries are clear.
Names overwhelmingly follow a verb_noun snake_case pattern such as list_repositories, get_commit, create_pull_request, and delete_webhook. The main inconsistency is mixing 'pr' abbreviations (approve_pr, get_pr_diff) with 'pull_request' forms (create_pull_request, list_pull_requests).
With 62 tools, the surface is very heavy for a single MCP server and exceeds the range where an agent can easily scan and choose tools. While the breadth reflects Bitbucket's API, the set could likely be consolidated into fewer operation groups.
Coverage is strong in several areas: repositories, PR review/merge actions, pipeline variables, webhooks, tags, and permissions have near-complete lifecycles. However, notable gaps remain, including branch creation/deletion, file write/update operations, project write operations, and PR metadata updates.