Atlassian Dc MCP Bitbucket logo

Atlassian Dc MCP Bitbucket

Connects AI agents to Bitbucket Data Center repositories and code through MCP.

Install Atlassian Dc MCP Bitbucket

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "atlassian-dc-mcp-bitbucket-2": {
      "command": "npx",
      "args": [
        "-y",
        "@atlassian-dc-mcp/bitbucket"
      ],
      "env": {
        "BITBUCKET_HOST": "YOUR_VALUE_HERE",
        "BITBUCKET_API_BASE_PATH": "YOUR_VALUE_HERE",
        "BITBUCKET_API_TOKEN": "YOUR_VALUE_HERE",
        "BITBUCKET_DEFAULT_PAGE_SIZE": "YOUR_VALUE_HERE",
        "ATLASSIAN_DC_MCP_CONFIG_FILE": "YOUR_VALUE_HERE",
        "ATLASSIAN_DC_MCP_REQUEST_TIMEOUT_MS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

atlassian-dc-mcp-bitbucket connects MCP-compatible clients to an Atlassian Bitbucket Data Center instance for repository and code operations. It runs as an npm-based stdio server and authenticates with a Bitbucket host plus API token, either from environment variables or saved local configuration. The interactive setup command validates the connection before storing credentials, while non-interactive flags support scripted and CI setup. Reach for it when an agent needs to work with Bitbucket Data Center rather than Bitbucket Cloud.

Use cases

  • Browse Bitbucket Data Center repositories with an AI agent
  • Inspect code stored in internal Bitbucket projects
  • Configure Bitbucket access for scripted or CI environments
  • Connect a Claude Desktop workspace to Bitbucket Data Center

Key features

  • MCP access to Bitbucket Data Center repositories and code
  • Interactive credential setup with connection validation
  • Non-interactive setup for scripts and CI
  • macOS Keychain credential storage
  • Environment-variable and shared dotenv configuration
  • Configurable request timeout and default page size

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

25/26 checks healthy over the last 90d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 7d ago via OSV.dev · @atlassian-dc-mcp/bitbucket (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars109Stargazers on the source repository.
npm downloads22kPackage downloads in the last 30 days.
Last commit7d agoMost recent push to the default branch.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Atlassian Dc MCP Bitbucket works

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:

Terminal
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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Atlassian Dc MCP Bitbucket

atlassian-dc-mcp-bitbucket is an MCP server that connects AI clients to Atlassian Bitbucket Data Center. Its main tools support interacting with repositories and code through the Model Context Protocol. It authenticates with a Bitbucket host and API token, supplied through setup, environment variables, or saved configuration.

Install and start it with `npx @atlassian-dc-mcp/bitbucket setup`, then launch `npx -y @atlassian-dc-mcp/bitbucket` from your MCP client configuration. Setup collects the host, API base path, page size, and token, and validates the connection before saving.

Configure credentials with the setup command or with `BITBUCKET_HOST` and `BITBUCKET_API_TOKEN`. You can use `BITBUCKET_API_BASE_PATH` instead of the host, or point `ATLASSIAN_DC_MCP_CONFIG_FILE` to an absolute dotenv file. Direct process variables override saved settings.

Yes, atlassian-dc-mcp-bitbucket works with Claude Desktop through its standard MCP configuration. Add an `atlassian-bitbucket-dc` entry that runs `npx -y @atlassian-dc-mcp/bitbucket`, then provide the Bitbucket host and token in the entry or use saved setup credentials.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewAtlassian Dc MCP Bitbucket AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/atlassian-dc-mcp-bitbucket-2?style=directory)](https://allmcps.com/mcp/atlassian-dc-mcp-bitbucket-2)
HTML Embed
<a href="https://allmcps.com/mcp/atlassian-dc-mcp-bitbucket-2"><img src="https://allmcps.com/api/badge/atlassian-dc-mcp-bitbucket-2?style=directory" alt="Atlassian Dc MCP Bitbucket on AllMCPs" /></a>