Power your agent
คำสั่งของผู้เผยแพร่เอง ไม่ใช่เอนด์พอยต์ของ PlugMCP
Host a copy with our keys and logs.
docker run -i --rm ghcr.io/fabianschurig/bitbucket-mcp:0.20.2Claude Code ไม่มีลิงก์ติดตั้งสำหรับคำสั่งแบบโลคัล ให้คัดลอกคำสั่งด้านล่างแล้วรันในเทอร์มินัล
BITBUCKET_USERNAME=<value> BITBUCKET_TOKEN=<secret> claude mcp add fabianschurig-bitbucket-cli -- docker run -i --rm ghcr.io/fabianschurig/bitbucket-mcp:0.20.2รันในเทอร์มินัล
{ "mcpServers": { "fabianschurig-bitbucket-cli": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/fabianschurig/bitbucket-mcp:0.20.2" ], "env": { "BITBUCKET_USERNAME": "<value>", "BITBUCKET_TOKEN": "<secret>" } } }}claude_desktop_config.json
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดLow-maintenance Bitbucket Cloud tooling built from the live OpenAPI spec: a CLI for software engineers, an MCP server for AI agents, and a Terraform provider for DevSecOps teams.
[!IMPORTANT]
https://github.com/FabianSchurig/bitbucket-cliis the canonical repository. If you found this project through theterraform-provider-bitbucketmirror, watch, star, file issues, and contribute inbitbucket-cli.
To install the CLI tool via our custom tap, tap the repository and explicitly trust the formula to reduce supply chain risks:
brew tap FabianSchurig/tap
brew trust --formula FabianSchurig/tap/bitbucket-cli
brew install bitbucket-cli
Or to install the MCP server:
brew tap FabianSchurig/tap
brew trust --formula FabianSchurig/tap/bitbucket-mcp
brew install bitbucket-mcp
(Note: If you previously tapped the old cask, you can safely untap via brew untap fabianschurig/tap before running the command).
Download the .deb package from the latest release and install it. Supported architectures: amd64, arm64.
TAG_URL=$(curl -fsSIL -o /dev/null -w '%{url_effective}' https://github.com/FabianSchurig/bitbucket-cli/releases/latest)
VERSION=${TAG_URL##*/}
VERSION=${VERSION%%\?*}
VERSION=${VERSION%%\#*}
VERSION=${VERSION#v}
ARCH=$(dpkg --print-architecture)
curl -LO "https://github.com/FabianSchurig/bitbucket-cli/releases/download/v${VERSION}/bb-cli_${VERSION}_${ARCH}.deb"
sudo dpkg -i "bb-cli_${VERSION}_${ARCH}.deb"
Replace bb-cli with bb-mcp to install the MCP server instead.
Download the .rpm package from the latest release and install it. Supported architectures: amd64, arm64.
TAG_URL=$(curl -fsSIL -o /dev/null -w '%{url_effective}' https://github.com/FabianSchurig/bitbucket-cli/releases/latest)
VERSION=${TAG_URL##*/}
VERSION=${VERSION%%\?*}
VERSION=${VERSION%%\#*}
VERSION=${VERSION#v}
ARCH=$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/')
curl -LO "https://github.com/FabianSchurig/bitbucket-cli/releases/download/v${VERSION}/bb-cli_${VERSION}_${ARCH}.rpm"
sudo rpm -i "bb-cli_${VERSION}_${ARCH}.rpm"
Replace bb-cli with bb-mcp to install the MCP server instead.
scoop bucket add bitbucket https://github.com/FabianSchurig/scoop-bucket
scoop install bb-cli
scoop install bb-mcp
winget install FabianSchurig.bb-cli
winget install FabianSchurig.bb-mcp
curl -fsSL https://raw.githubusercontent.com/FabianSchurig/bitbucket-cli/main/install.sh | sh
See install.sh options for version selection, binary choice (bb-cli, bb-mcp, or all), and custom install directories.
For full installation details see the CLI usage guide and the MCP usage guide.
This repository keeps Bitbucket Cloud tooling maintainable by generating most of the surface area from the live Bitbucket OpenAPI spec.
schema/ can be hand-authored for endpoints that are not in Bitbucket's public OpenAPI spec (for example the project-level branch-restrictions endpoint exposed only via https://bitbucket.org/!api/internal/...). The generators and runtime treat them identically — schema paths may use absolute URLs and the dispatcher passes them through unchanged.flowchart LR
A[Live Bitbucket OpenAPI spec] --> B[enrich_spec.py]
B --> C[partition_spec.py]
C --> D[schema/*-schema.yaml]
D --> E[oapi-codegen models]
D --> F[CLI generator]
D --> G[MCP generator]
D --> H[Terraform generator]
E --> I[Shared generated types]
F --> J[bb-cli]
G --> K[bb-mcp]
H --> L[terraform-provider-bitbucket]
I --> J
I --> K
I --> L
M[Hand-written runtime\nauth, dispatch, output, MCP handler, TF runtime] --> J
M --> K
M --> L
In practice:
flowchart TD
A[push / pull_request] --> B[ci.yml]
A --> C[terraform-tests.yml]
D[schedule / manual] --> E[schema-sync.yml]
E --> F[Fetch live spec]
F --> G[Regenerate code and docs]
G --> H[Build and test]
H --> I[Tag new version]
I --> J[release.yml]
J --> K[docker.yml]
I --> L[terraform-release.yml]
K --> M[Publish to MCP Registry]
ci.yml: builds, lints, vets, runs Go tests, and sends analysis to SonarQube Cloud.terraform-tests.yml: runs mock-based Terraform acceptance and terraform test suites, plus real API tests when credentials exist. See docs/e2e-coverage.md for the current list of endpoints exercised by the real-API tests.schema-sync.yml: daily/manual sync that fetches the live Bitbucket spec, regenerates generated artifacts, rebuilds docs, tests everything, and tags a release when the schema changed.release.yml: publishes tagged binary releases via GoReleaser.docker.yml: builds multi-arch container images for bb-cli and bb-mcp, pushes them to GHCR, publishes their SBOM and CVE reports (see Supply chain: SBOM and CVE reports), and publishes the bb-mcp server to the MCP Registry.terraform-release.yml: mirrors the tagged source into terraform-provider-bitbucket and publishes the Terraform provider release.The live OpenAPI document is treated as an input, not as an authority to delete a working API group because of a transient omission. Three mechanisms keep the daily sync from breaking published surface or itself:
partition_spec.py
preserves its existing populated schema; a genuinely empty or new group is
still written normally.schema/operation-ids.json, keyed by
"<method> <path>". An operation keeps its id forever, and ids of removed
operations stay reserved — so a sibling endpoint can never inherit an id and
silently rename a shipped CLI command, MCP tool, or CRUDConfig reference.partition_spec.py carries such operations
forward verbatim from the committed schema, annotated x-bb-cli-retained: true
so the schema diff shows exactly what upstream stopped publishing. Retiring one
for good is a deliberate act: delete it from schema/*-schema.yaml, and the
invariant tests then flag any hand-maintained mapping (for example in
CRUDConfig) that still references it.Acceptance tests in internal/tfprovider/acceptance_test.go are hand-written and
are never deleted by schema generation. Generated Terraform fixtures are
regenerated from the surviving resource groups, while the schema-sync build and
test gate, including the mock Terraform acceptance suites, must pass before any
change is committed or released. The generated
real-API coverage report makes missing group coverage
visible without requiring manual bookkeeping.
Every released container image ships with a Software Bill of Materials and a vulnerability report in standard formats. Both are produced from the exact image digest that was pushed to GHCR.
The SBOM is also attached to the image as a signed, digest-bound GitHub attestation, so consumers can verify and fetch it without any access to this repository:
gh attestation verify oci://ghcr.io/fabianschurig/bitbucket-mcp:latest --owner FabianSchurig
gh attestation download oci://ghcr.io/fabianschurig/bitbucket-mcp:latest --owner FabianSchurig
Runtime images are built FROM scratch and contain only the static binary plus CA certificates, so the SBOM is deliberately small and there is no OS package surface to patch.
Vulnerability scan results are additionally uploaded to GitHub code scanning (categories docker-bitbucket-cli and docker-bitbucket-mcp) for maintainers, and the Go module tree is checked by govulncheck in security.yml.
DrFaust92/terraform-provider-bitbucketThis project optimizes for breadth, maintenance, and shared infrastructure across interfaces. If you want a heavily hand-modeled Terraform UX, the DrFaust92 provider may feel more familiar. If you want one maintained pipeline that keeps Terraform, CLI, and MCP aligned with Bitbucket Cloud, this repository is designed for that.
Use the short guides on this first page to get started, then switch to the detailed docs for the interface you need.
TestAccRealAPI_* tests, and which are still missing coverage.The Terraform documentation under docs/ is generated. The root README stays focused on orientation, links, architecture, maintenance, and contribution entry points.
bitbucket-cli repository.This provides a go bitbucket cli bb-cli, an mcp server bb-mcp and a terraform provider. All by focusing on low maintenance using auto generation from the official OpenAPI Spec.
{ "mcpServers": { "fabianschurig-bitbucket-cli": { "command": "docker", "args": [ "run", "-i", "--rm", "ghcr.io/fabianschurig/bitbucket-mcp:0.20.2" ], "env": { "BITBUCKET_USERNAME": "<value>", "BITBUCKET_TOKEN": "<secret>" } } }}เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ผู้เผยแพร่ระบุตัวแปรสภาพแวดล้อมเหล่านี้: BITBUCKET_USERNAME, BITBUCKET_TOKEN
Bitbucket Cli ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 This provides a go bitbucket cli bb-cli, an mcp server bb-mcp and a terraform provider. All by focusing on low maintenance using auto generation from the official OpenAPI Spec.