Bitbucket Server MCP
Related Servers
Alternatives to Bitbucket Server MCP
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.195,589MIT
- AlicenseBqualityAmaintenanceMCP server with 58 tools for Bitbucket API operations. Manage repositories, pull requests, pipelines, branches, commits, deployments, webhooks, and more.582MIT
- AlicenseNot gradedqualityCmaintenanceA comprehensive MCP server for Jira, Confluence, and Bitbucket that supports both Cloud and Data Center deployments. It provides 136 tools for managing issues, searching documentation, and handling Git workflows like pull requests and pipelines.6MIT
- 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
- AlicenseBqualityBmaintenanceMCP server for Bitbucket Server integration, enabling project, repository, pull request, source code, branch, and code review operations via the Bitbucket Server APIs.2713MIT
TDQS
Scored across 57 tools
Tools are largely distinct, but there is redundancy between create_pull_request (which has a draft parameter) and create_draft_pull_request; also browse_files vs list_files could confuse agents. Overall, most tools have clear boundaries.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_projects, get_commit, create_branch). No mixing of conventions or irregular naming.
With 57 tools, the surface is overly large for a typical Bitbucket server integration. Many specialized tools (e.g., for attachments, versioned comments) contribute to bloat; a more focused set of 25-35 tools would be more appropriate.
Covers the core PR lifecycle, commits, branches, repos, projects, search, and comments comprehensively. Minor gaps: no delete_branch, delete_repository, or update_repository tools, but these are not critical for most workflows.