Native async Bitbucket Server/Data Center MCP server
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"bitbucket-mcp-atlassian","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Bitbucket Server MCP Native Python MCP server for Bitbucket Server and Data Center. It uses the Bitbucket REST API directly with a single self-contained runtime. ## Install and run Install [uv](https://docs.astral.sh/uv/), copy `.env.example` to `.env`, and set the Bitbucket URL and credentials: ```bash cp .env.example .env uv sync uv run bitbucket-mcp ``` Use a personal access token with `BITBUCKET_TOKEN`, or set both `BITBUCKET_USERNAME` and `BITBUCKET_PASSWORD`. `BITBUCKET_URL` is the Bitbucket web base URL, for example `https://bitbucket.example.com` (the client appends `/rest/api/1.0`). Set `BITBUCKET_VERIFY_TLS=false` only for a deliberately trusted test certificate. `BITBUCKET_TIMEOUT`, `BITBUCKET_MAX_RETRIES`, and `BITBUCKET_TRANSPORT` (`stdio`, `sse`, or `streamable-http`) are also supported. Example stdio MCP configuration: ```json { "mcpServers": { "bitbucket": { "command": "uv", "args": ["run", "--directory", "/absolute/path/to/mcp-server-wrapper-bitbucket", "bitbucket-mcp"], "env": {"BITBUCKET_URL": "https://bitbucket.example.com", "BITBUCKET_TOKEN": "your-token"} } } } ``` ## Tools The server currently exposes 23 tools, organized by capability: - Projects and repositories: `list_projects`, `get_project`, `list_repositories`, `get_repository` - Pull requests: `create_pull_request`, `get_pull_request`, `list_pull_requests`, `update_pull_request`, `merge_pull_request`, `decline_pull_request` - Pull-request discussion and review: `add_comment`, `get_comments`, `get_diff`, `get_reviews` - Source history: `list_branches`, `list_commits`, `get_commit`, `get_file`, `browse_files` - Users and access: `list_users`, `get_user`, `list_permissions` - Builds and CI: `list_builds` All calls use Bitbucket Server/Data Center REST API v1.0 paths and return the API's JSON (or text for diffs and files), preserving pagination fields where Bitbucket supplies them. Write operations are limited to pull-request creation, updates, mer…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.