Atlassian Bitbucket MCP Server
Related Servers
Alternatives to Atlassian Bitbucket MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to list and retrieve repositories, fetch and create pull requests, and work with Bitbucket Cloud and Server APIs.6,993 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Bitbucket Cloud and Server APIs, including listing and retrieving repositories and fetching, creating, and viewing pull requests.6,993 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to access and manage repositories, pull requests, and related resources through Bitbucket Cloud and Server APIs.6,993 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Bitbucket Cloud and Server APIs to list and retrieve repositories, fetch and create pull requests, and perform other repository operations.6,993 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to list and retrieve repositories, inspect and create pull requests, and page through related Bitbucket data via Cloud and Server APIs.6,993 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Bitbucket Cloud repositories, allowing users to manage pull requests, comments, tasks, and branches through natural language commands.6,993 npm1MIT
TDQS
Scored across 19 tools
Each tool has a clearly distinct purpose. The action-noun pattern (e.g., 'add_pr_comment' vs 'add_pr_inline_comment') ensures no ambiguity between similar operations.
All tools follow the 'bitbucket_<verb>_<noun>' pattern using snake_case. The naming is perfectly uniform and predictable.
With 19 tools, the set is well-scoped for a Bitbucket server. It covers projects, repositories, pull requests, and comments without being overwhelming.
The tool set heavily focuses on reading and commenting on pull requests and repositories, but lacks create/update/delete operations for repositories and projects, as well as merge/decline for pull requests. This leaves notable gaps for full lifecycle management.