A hardened MCP server that exposes Bitbucket Data Center operations to AI coding assistants
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-dc-mcp","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-dc-mcp A hardened [Model Context Protocol](https://modelcontextprotocol.io) server that exposes Bitbucket Data Center operations to AI coding assistants like Claude Code, Claude Desktop, and GitHub Copilot. > **On-premise only.** This server targets Bitbucket **Data Center** > (self-hosted), not Bitbucket Cloud. If you run `bitbucket.org`, use a > Bitbucket Cloud MCP server instead. ## Why this exists Most AI coding assistant integrations assume SaaS deployments: Jira Cloud, Bitbucket Cloud, GitHub.com. But a large portion of enterprise development happens behind corporate firewalls, on self-hosted Atlassian Data Center, where cloud connectors cannot reach. This project exists to fill that gap. It is a small, auditable, locally runnable MCP server that an AI assistant can call to interact with an on-premise Bitbucket Data Center instance, with a security posture that is suitable for enterprise environments. ## What it does Exposes seventeen tools via the MCP protocol, split into read and write operations. Write tools are tagged `[WRITE]` in their description so the MCP client's human approval UI clearly distinguishes them from read-only tools. ### Read tools | Tool | Description | |---|---| | `bitbucket_get_repo_info` | Fetch repository metadata (name, default branch, description) | | `bitbucket_list_branches` | List branches of a repository | | `bitbucket_list_files` | List files in a repository or subdirectory without cloning | | `bitbucket_get_file_content` | Read a file from the remote without cloning | | `bitbucket_list_pull_requests` | List pull requests by state (OPEN, DECLINED, MERGED, ALL) | | `bitbucket_get_pull_request` | Get full details of a pull request by ID | | `bitbucket_get_pull_request_diff` | Get the git-style unified diff of a pull request | | `bitbucket_get_pull_request_comments` | Get all comments on a pull request | ### Write tools | Tool | Description | |---|---| | `bitbuc…
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.