Skip to main content
Glama
garc33

Bitbucket Server MCP

by garc33

Related Servers

Alternatives to Bitbucket Server MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with Bitbucket Server (Data Center) via MCP, supporting reading pull requests and diffs, drafting and submitting reviews with verdicts, posting tasks, browsing code and commits, and managing pull requests.
      1
      ISC
    • A
      license
      B
      quality
      C
      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
      29 npm
      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
      -
    • 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,929 npm
      MIT

    TDQS

    A3.5/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., add_comment vs add_comment_inline, approve vs unapprove). Some overlap exists between get_activities, get_comments, and get_reviews, but descriptions clarify the granularity differences. Only minor confusion is possible when choosing between activity-related tools.

    Naming Consistency4/5

    Nearly all tools follow a consistent verb_noun snake_case pattern (get_pull_request, list_branches, create_pull_request, delete_comment). The only deviation is 'search', which lacks a noun, but it remains readable and predictable overall.

    Tool Count3/5

    With 27 tools, the set is on the heavy side, exceeding the typical 3-15 range. While each tool serves a distinct purpose, the volume feels borderline for a single MCP server and could overwhelm agents without careful grouping.

    Completeness3/5

    The surface covers pull request lifecycle, comments, reviews, branches, commits, and file reading well. However, notable gaps exist: no branch creation, no repository creation/deletion, and no file write or commit creation operations, which limits end-to-end contribution workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive