Skip to main content
Glama
inconcept

Bitbucket MCP

by inconcept
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Bitbucket MCP

No user-submitted related servers found.

    Related Servers

    • bitbucket-mcp

      matt-nann
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Bitbucket Cloud that enables reviewing, managing, and merging pull requests, assigning reviewers by name, reading files at a ref, and inspecting pipeline status from any MCP client.
      14
      MIT

    • Bitbucket MCP Server

      zhanglc
      A
      license
      B
      quality
      D
      maintenance
      An 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.
      19
      5,589 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.4/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a distinct resource/action: pull request lifecycle, comments, approvals, statuses, and default reviewers are all cleanly separated. Even closely related actions like approve, request changes, and decline are clearly differentiated by name and description.

    Naming Consistency4/5

    The set overwhelmingly follows a verb_noun snake_case pattern, which makes it predictable. The main inconsistency is mixing 'pr' and 'pull_request' (e.g., list_pull_requests vs. list_pr_comments, get_pull_request vs. get_pr_comment), so it is not perfectly uniform.

    Tool Count3/5

    At 23 tools, the server is in the heavy range. Each tool has a distinct purpose, but the granular review-state operations and default reviewer management could feel bloated compared to a leaner PR-focused server.

    Completeness4/5

    The server covers the core Bitbucket pull request workflow well: PR CRUD, merging/declining, comments, approvals, statuses, and default reviewers. Minor gaps exist, such as no single-repository fetch and no way to delete a PR comment, but these are unlikely to block common workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources