Skip to main content
Glama
pdogra1299

Bitbucket MCP Server

by pdogra1299
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Bitbucket MCP Server

No user-submitted related servers found.

    Related Servers

    • 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
      8,638 npm
      MIT

    • 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

      nbhson
      A
      license
      B
      quality
      B
      maintenance
      MCP server for Bitbucket Server integration, enabling project, repository, pull request, source code, branch, and code review operations via the Bitbucket Server APIs.
      27
      17 npm
      MIT

    • Bitbucket MCP

      inconcept
      A
      license
      B
      quality
      C
      maintenance
      An MCP server for Bitbucket Cloud that enables managing pull requests, branches, and repositories in natural language from any MCP-capable client.
      23
      164 npm
      4
      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/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or actions (PRs, comments, branches, commits, files, projects/repos). Minor overlap exists between list_pr_commits and list_branch_commits, and between get_pull_request_diff and get_commit_detail, but descriptions make the boundaries usable.

    Naming Consistency4/5

    Predominantly consistent snake_case verb_noun naming across the set. Minor deviations include 'pr' in list_pr_commits versus 'pull_request' elsewhere, and manage_comment is less operation-specific than neighboring names.

    Tool Count3/5

    20 tools is on the heavy side for a PR-centric Bitbucket server; the rubric treats 16-25 tools as borderline. Most operations are useful, but the set could likely be consolidated without losing important capability.

    Completeness4/5

    Core PR lifecycle coverage is strong: list/get/create/update/merge/decline, comments and tasks, review status, diffs, commits, branches, file/directory reads, and project/repository listing. Missing write operations outside PRs (create_branch, create_repository, file write) and some repository-level get/update operations are minor gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources