Skip to main content
Glama
jabdon00

bitbucket-standalone-mcp

by jabdon00
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to bitbucket-standalone-mcp

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.
      4 npm
      MIT

    • mcp-bitbucket

      cuonghuunguyen
      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

    • Bitbucket DC MCP Server

      lvluu
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible AI clients to interact with a Bitbucket Data Center instance through its REST API v1.0, exposing 55 tools for projects, repositories, pull requests, comments, diffs, tasks, branches, tags, commits, files, and build statuses. Supports stdio and streamable HTTP transports with token or basic authentication and compacted tool results.
      611 npm
      MIT

    • Bitbucket MCP Server

      nbhson
      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
      10 npm
      MIT
    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.4/5.0

    Scored across 41 tools

    Disambiguation4/5

    Most tools map to a clear resource+action (repositories, branches, pull requests, files, commits), and the bb_ prefix plus descriptive names help separate them. The main ambiguities are bb_get_file vs bb_raw_file, which both read file content, and the several diff tools, but their parameter scopes and descriptions are usually enough to disambiguate.

    Naming Consistency4/5

    All tools share a consistent bb_ prefix and overwhelmingly follow a verb_noun pattern such as list_repositories, create_pull_request, and delete_file. Minor deviations like bb_raw_file, bb_application_properties, and bb_detect_repo break the pattern slightly but remain understandable.

    Tool Count2/5

    41 tools is well into the heavy range for a single MCP server, and the count is inflated by overlapping file readers, multiple diff variants, and a nonfunctional bb_search_code tool. While each tool is individually scoped, the surface is larger than an agent needs for most workflows.

    Completeness4/5

    The tool set covers the core developer lifecycle well: project/repo listing, branches, full pull request management with comments, diffs, commits, file read/write, build statuses, and local repo detection. Notable gaps such as repository/project update/delete, tags, and code search are present but do not block the primary Bitbucket workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources