Skip to main content
Glama
Stan15

bucket-mcp

by Stan15
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to bucket-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • Bitbucket MCP Server

      jlromano
      A
      license
      B
      quality
      D
      maintenance
      Enables LLMs to interact with Bitbucket repositories to manage pull requests, branches, and commits through the Model Context Protocol. It supports repository operations such as searching code, accessing file contents, and comparing branches using natural language.
      16
      3,208 npm
      MIT
    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.2/5.0

    Scored across 26 tools

    Disambiguation4/5

    Tools are organized by resource, and the diff/diffstat split is clearly explained, so the most similar pairs remain distinguishable. A few overlaps like PR-level vs commit-level statuses could cause an agent to pick the wrong variant, but the descriptions generally prevent real ambiguity.

    Naming Consistency4/5

    The bitbucket_<resource>_<action> pattern is used consistently, giving the set a uniform and predictable shape. Minor outliers like bitbucket_whoami and bare-noun operations such as diffstat or merge_status keep it from being a perfect pattern.

    Tool Count2/5

    With 26 tools, the surface crosses the 25-tool threshold and includes several near-duplicate pairs for diff/diffstat and statuses. A more curated set would be easier to navigate, especially since one tool, merge_status, lacks its corresponding merge action.

    Completeness2/5

    The pull request workflow is incomplete: merge_status references a merge tool that is not present, and pull_request_create only creates drafts with no way to mark them ready, update, or merge. Repositories, branches, and tags are also read-only, leaving common lifecycle actions out of reach.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources