Skip to main content
Glama
maggiechew

bitbucket-mcp

by maggiechew
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to bitbucket-mcp

No user-submitted related servers found.

    Related Servers

    • bucket-mcp

      Stan15
      A
      license
      B
      quality
      B
      maintenance
      Enables Bitbucket Cloud code review and PR workflows from Claude Code, covering repos, pull requests, commits, branches, file browsing, code search, and workspace/user discovery.
      26
      MIT

    • Bitbucket MCP

      SamtheIII
      A
      license
      A
      quality
      D
      maintenance
      Connects Claude Desktop and Claude Code to Bitbucket Cloud, enabling searching PRs, commits, diffs, and file content for AI-assisted bug triage and impact analysis.
      8
      38 npm
      ISC

    • bitbucket-server-mcp

      Upendrasengar
      A
      license
      A
      quality
      B
      maintenance
      Enables to interact with Bitbucket Server repositories, pull requests, and code reviews, including file browsing, PR management, and review actions through natural language.
      59
      13 npm
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 21 tools

    Disambiguation4/5

    Each tool targets a distinct resource and action, and the pull request and pipeline namespaces are clearly separated. Minor overlap exists between getPullRequestComments and getPullRequestActivity, and between getPullRequestDiff and getPullRequestDiffStat, but the descriptions are clear enough to resolve ambiguity.

    Naming Consistency4/5

    Tool names consistently use camelCase and follow a clear verb_noun pattern, with list/get/create/update/delete verbs and PR or pipeline context prefixes. There are minor inconsistencies like addPullRequestComment vs createPullRequest and convertToDraft, but the naming remains predictable overall.

    Tool Count3/5

    At 21 tools, the server is on the heavy side and covers two fairly broad domains: pull requests and pipelines. The count feels borderline; some tools like getPullRequestDiff and getPullRequestDiffStat could potentially be consolidated, though each still serves a distinct use case.

    Completeness3/5

    The pull request lifecycle covers creation, updating, drafts, comments, diffs, commits, and activity, but core Bitbucket actions like merge, decline, and approve are missing. Pipeline coverage is solid with run, stop, steps, and logs, but the PR gaps prevent full workflow completion.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources