Bitbucket Cloud MCP Server
Related Servers
Alternatives to Bitbucket Cloud MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Bitbucket Cloud workspaces, repositories, branches, commits, and pull requests through tools for listing, retrieving, creating, commenting, searching, and cloning via the Bitbucket REST API.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to connect to Bitbucket Cloud and interact with workspaces, repositories, branches, commits, files, and pull requests through MCP tools, including listing, getting, creating, commenting, searching, reviewing, approving, declining, and merging PRs.MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with Bitbucket Cloud REST API 2.0, supporting pull requests, pipelines, logs, and repository cloning through MCP tools.36 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Bitbucket Cloud workspaces, repositories, branches, commits, and pull requests through generic GET, POST, PUT, PATCH, DELETE, and clone tools, including reading PR diffs, adding comments, approving, merging, and filtering responses with JMESPath. It connects LLMs directly to version control workflows so tasks like code review, repository search, and PR management can be done in natural language.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Bitbucket Cloud workspaces, repositories, and pull requests through generic GET, POST, PUT, PATCH, DELETE, and clone tools, covering branches, commits, file contents, diffs, issues, pipelines, and deployments. Supports JMESPath filtering and a token-efficient output format to reduce token costs.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to read and manage Bitbucket workspaces, repositories, branches, commits, files, and pull requests through the Bitbucket Cloud REST API, including commenting, approving, merging, comparing branches, and cloning repos. It exposes generic GET, POST, PUT, PATCH, and DELETE tools with JMESPath filtering and token-efficient output for any endpoint.-
TDQS
Scored across 34 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the Bitbucket Cloud domain. For example, 'get_pull_request' retrieves details while 'approve_pull_request' performs an action, and tools like 'list_pr_comments' vs 'add_pr_comment' handle different aspects of PR comments without overlap.
All tools follow a consistent verb_noun pattern with snake_case throughout, such as 'create_branch', 'list_issues', 'update_pull_request'. There are no deviations in naming conventions, making the set highly predictable and readable.
With 34 tools, the count is borderline high for a single server, potentially feeling heavy and overwhelming for agents. While it covers many Bitbucket Cloud operations, a more modular approach might improve usability without sacrificing functionality.
The tool surface provides comprehensive CRUD and lifecycle coverage for repositories, branches, commits, issues, pull requests, pipelines, and code search. It includes all essential operations like create, get, list, update, delete, and specific actions such as merge, approve, and trigger, with no obvious gaps for the domain.