Bitbucket Cloud MCP Server
Related Servers
Alternatives to Bitbucket Cloud MCP Server
No user-submitted related servers found.
Related Servers
- 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
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Bitbucket Cloud workspaces, repositories, branches, commits, issues, pipelines, and pull requests through MCP tools for listing, reading, creating, updating, commenting, searching, comparing, approving, merging, and cloning. It connects LLMs directly to version control and repository workflows via standard API paths and configurable authentication.-
- AlicenseBqualityDmaintenanceMCP server for Bitbucket Cloud that enables AI agents to manage repositories, branches, pull requests, and deployments via typed tools.1744 npmISC
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Bitbucket Cloud workspaces, repositories, pull requests, commits, branches, diffs, comments, issues, pipelines, and deployments through MCP tools for listing, reading, creating, updating, deleting, searching, commenting, and cloning via the Bitbucket API.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Atlassian Bitbucket Cloud workspaces, repositories, branches, commits, pull requests, issues, pipelines, and deployments through generic API tools and repository cloning. Supports natural-language code search, review, commenting, and workflow automation via the MCP interface.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Atlassian Bitbucket Cloud workspaces, repositories, and pull requests through MCP tools for listing, getting, commenting, searching, and managing version control workflows.MIT
TDQS
Scored across 33 tools
Each tool targets a distinct resource and action, with clear prefixes and specific nouns. Even within the large set of pull request tools, each has a unique purpose (e.g., approve vs. merge vs. request changes). No two tools are easily confused.
All tools follow the 'bb_verb_noun' pattern consistently, using snake_case. Verbs are well-chosen (create, get, list, delete, update, etc.) and nouns are specific (pull_request, issue, branch, etc.). No mixing of conventions.
33 tools cover a wide range of Bitbucket functionality (repos, PRs, issues, pipelines, search, etc.). While on the higher end, the count is justified by the domain's complexity. Some tools could be consolidated (e.g., diff and diffstat), but overall it's well-scoped.
Pull request coverage is thorough (CRUD, comments, diff, activity). Issues lack update/delete, and repositories lack create/delete. Pipelines are missing cancel/stop. These are notable but not critical gaps, as the core workflows are covered.