Skip to main content
Glama

Related Servers

Alternatives to bitbucket-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to connect to Bitbucket Cloud and interact with workspaces, repositories, branches, commits, files, and pull requests through MCP tools, including listing, getting, creating, commenting, searching, reviewing, approving, declining, and merging PRs.
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP-compatible clients to read repositories and source code from Bitbucket. Provides tools for listing workspaces and repositories, browsing directories, reading files, searching code, and inspecting commits and pull requests.
      12
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Bitbucket Cloud workspaces, repositories, and pull requests by providing MCP tools for listing, reading, creating, commenting, searching, and cloning.
      MIT
    • F
      license
      B
      quality
      B
      maintenance
      Enables interaction with a Bitbucket Server/Data Center instance, exposing its REST v1.0 API as MCP tools to manage projects, repositories, branches, pull requests, comments, diffs, commits, files, search, and build status.
      41
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to interact with Bitbucket Cloud workspaces, repositories, pull requests, branches, commits, and code for listing, retrieval, commenting, searching, diffing, and repository cloning through MCP tools.
      -

    TDQS

    A3.7/5.0

    Scored across 18 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: local profile operations are clearly separated from Bitbucket API operations, and list/get/create/update verbs are consistently paired with specific objects like workspaces, repositories, branches, pull requests, and comments. There is no meaningful overlap or ambiguous boundary between tools.

    Naming Consistency4/5

    Tool names mostly follow a consistent list_/get_/create_/update_/set_/clear_ verb_noun pattern, which is predictable and readable. The main deviation is mixing 'pr' and 'pull_request' across related tools (e.g. get_pr_commits vs get_pull_request), which slightly weakens consistency.

    Tool Count4/5

    At 18 tools, the set is slightly above the ideal 3–15 range, but each tool addresses a distinct need across workspaces, repositories, branches, pull requests, comments, and local profile configuration. The count feels slightly heavy but not bloated.

    Completeness3/5

    The read side is well covered, and pull request creation plus commenting are supported, but notable lifecycle operations are missing: merge/approve/decline for pull requests, repository/branch write operations, and profile creation/deletion. These gaps prevent full CRUD/lifecycle coverage of the apparent Bitbucket domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues