Skip to main content
Glama
phpl

bitbucket-mcp-server

by phpl
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to bitbucket-mcp-server

No user-submitted related servers found.

    Related Servers

    • stash-mcp

      schwarztim
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables interaction with Bitbucket Server/Data Center (Stash) for project and repository discovery, pull request management, code review, and code search.
      2 npm
      MIT

    • Bitbucket MCP Server

      chzkyy
      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

    • bitbucket-standalone-mcp

      jabdon00
      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
      -

    • bitbucket-mcp

      Unofficial-Warp
      F
      license
      Not graded
      quality
      D
      maintenance
      Exposes Bitbucket Cloud repository and pull request data as tools consumable by any MCP-compatible client, with per-request authentication via the caller's own Bitbucket API token.
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools clearly target distinct resources or specific aspects (e.g., PR activities vs. commits). The only real ambiguity is between get_pull_request_diff and get_pull_request_file_diff, which both involve diffs but with different output structures, so an agent could be unsure which to use.

    Naming Consistency4/5

    The naming pattern is largely consistent, using get_ for single items and list_ for collections. However, get_inbox_pull_requests and get_all_users are list operations that use get_ instead of list_, which is a minor deviation from the dominant verb convention.

    Tool Count3/5

    With 24 tools, this server is on the heavy side, fitting the borderline range of 16-25. The count is driven by 10 pull-request-related tools, which feel numerous even though each has a distinct purpose. A more consolidated set would be more appropriate.

    Completeness2/5

    The server is entirely read-only, lacking any create, update, delete, merge, or comment capabilities for repositories or pull requests. This is a significant gap for a Bitbucket integration, preventing agents from completing common lifecycle workflows like approving or merging a PR.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources