# atlassian-dc-mcp-bitbucket [Health: Active]

**Category:** 🔄 Version Control  
**Repository:** https://github.com/b1ff/atlassian-dc-mcp  
**GitHub Stars:** 109  
**npm Downloads (last month):** 22171  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/atlassian-dc-mcp-bitbucket-2

## Description
MCP server for Atlassian Bitbucket Data Center - interact with repositories and code

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "atlassian-dc-mcp-bitbucket": {
    "command": "npx",
    "args": ["-y","@atlassian-dc-mcp/bitbucket"],
    "env": {
      "BITBUCKET_HOST": "",
      "BITBUCKET_API_BASE_PATH": "",
      "BITBUCKET_API_TOKEN": "",
      "BITBUCKET_DEFAULT_PAGE_SIZE": "",
      "ATLASSIAN_DC_MCP_CONFIG_FILE": "",
      "ATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS": ""
    }
  }
}
```

**Requires environment variables:** `BITBUCKET_HOST`, `BITBUCKET_API_BASE_PATH`, `BITBUCKET_API_TOKEN`, `BITBUCKET_DEFAULT_PAGE_SIZE`, `ATLASSIAN_DC_MCP_CONFIG_FILE`, `ATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What atlassian-dc-mcp-bitbucket does

atlassian-dc-mcp-bitbucket exposes Bitbucket Data Center through the Model Context Protocol, allowing a compatible AI client to interact with repositories and code through MCP tools. It is part of a broader community-maintained package set that also includes separate Jira and Confluence servers; the Bitbucket package is installed and launched independently.

The project is not affiliated with, endorsed by, or supported by Atlassian. It is intended for teams operating an Atlassian Data Center deployment and belongs naturally in a version-control toolchain where an agent needs access to internal Bitbucket resources.

## How it works

The package runs through `npx` as an MCP process. A client starts `@atlassian-dc-mcp/bitbucket`, and the process resolves its Bitbucket connection settings before serving requests. Configuration can come from direct process environment variables, an explicitly selected dotenv file, the product-specific home configuration file, or the macOS Keychain for the token. Higher-priority sources override lower-priority ones.

Bitbucket requests use a 30-second default timeout. Set `ATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS` to a positive millisecond value when a different limit is needed. Keychain token reads on macOS are cached during initialization rather than performed for every tool call.

## Setup and configuration

Run the package's setup command once:

```bash
npx @atlassian-dc-mcp/bitbucket setup
```

The prompts accept the Bitbucket host, API base path, default page size, and API token. Setup checks obvious input errors and makes a timed authenticated request before saving. For automation, pass `--host`, `--api-base-path`, `--token`, or `--default-page-size` and add `--non-interactive`; missing required values or a failed validation causes that mode to exit with an error.

On macOS, the token is stored in the login Keychain. Linux stores credentials in `~/.atlassian-dc-mcp/bitbucket.env` with user-only POSIX permissions, while Windows uses the equivalent file under the user profile. Host, API base path, and page-size settings are kept in the home configuration file. After a successful macOS Keychain write, the token is removed from the less-secure home-file copy.

A client can also provide `BITBUCKET_HOST` and `BITBUCKET_API_TOKEN`, or replace the host with `BITBUCKET_API_BASE_PATH`, which accepts a complete API base URL. `ATLASSIAN_DC_MCP_CONFIG_FILE` selects an absolute-path shared dotenv file; direct environment variables take precedence.

## Limitations and notes

The server targets Atlassian Bitbucket Data Center, not a documented Bitbucket Cloud configuration. The host value should contain only the domain and optional port when using the host setting; the API-base-path alternative carries the protocol and base URL. Configuration can be saved locally with setup, so clients do not need inline environment variables after that step. Review local credential storage and access controls before deploying it on shared machines.

_Full upstream README: https://allmcps.com/mcp/atlassian-dc-mcp-bitbucket-2/readme_