No user-submitted related servers found.
Scored across 17 tools
Most tools have clearly distinct resource/action targets, especially across PRs, pipelines, comments, and repositories. The only mild overlaps are health-check vs get-metrics and the dual list/get pattern used by repositories, pull-requests, commits, and pipelines, but the descriptions clarify parameter behavior.
All names use kebab-case, but the set mixes noun-only resource names (repositories, commits, pr-comments) with verb_noun names (create-pull-request, get-pr-diff) and an action-parameter tool (pipeline-steps). The convention is readable but not uniform.
17 tools is slightly above the ideal 3-15 range but still reasonably scoped for Bitbucket's breadth across repositories, commits, branches, PRs, pipelines, issues, and search. Each major area has coverage, with no obvious duplicate tools.
Core read and some write workflows are covered for PRs and pipelines, but there are notable gaps: no create/update issue, no PR approval or merge, no branch creation/deletion, and no source file browsing. Agents can still handle many tasks but will hit dead ends for common Bitbucket lifecycle operations.