bitbucket-data-center-mcp

A Model Context Protocol (MCP) server for Bitbucket Data Center, designed to improve developer productivity.

Prerequisites

• Node.js v18 or higher
• pnpm v8 or higher

Environment Variables

Variable	Required	Description
BITBUCKET_URL	Yes	Base URL of your Bitbucket Data Center instance (e.g. https://bitbucket.example.com)
BITBUCKET_TOKEN	Yes	Personal access token for authentication
DEBUG	No	Set to any value to enable debug logging

Installation

git clone https://github.com/peterknezek/bitbucket-data-center-mcp.git
cd bitbucket-data-center-mcp
pnpm install

Available Tools

Name	Description
get_pr_comments	Fetches all unresolved inline review comments for the open PR on the current branch, including full reply threads rendered as nested trees. Pass repoPath (from git rev-parse --show-toplevel) to auto-detect project, repo, and branch via git and enable clickable file links in Cursor.
create_pull_request	Creates a pull request on Bitbucket Data Center. Auto-detects project, repo, and branch from repoPath. Auto-generates a PR title from branch naming convention (<type>/<taskId>_<description>), resolves the default target branch, validates that the branch has been pushed, and optionally adds reviewers and draft status.
reply_to_pr_comment	Posts a reply to a specific pull request comment by its ID. Use the comment IDs returned by get_pr_comments. Useful for acknowledging a review comment or explaining what fix was applied. Pass repoPath (from git rev-parse --show-toplevel) to auto-detect project, repo, and branch.

Available Prompts

Name	Description
review-pr-comments	Fetches and displays all unresolved PR review comments as formatted, navigable links
create-pull-request	Analyzes the current branch, drafts a PR title and short description following branch naming conventions, confirms with the user, then creates the pull request on Bitbucket Data Center.
rebase-onto-main	Detects the default branch (main or master), fetches the latest changes, rebases the current branch onto it, resolves any conflicts, and force-pushes.

Connecting to an MCP Client

Cursor

1. Open Cursor settings (Cmd/Ctrl + ,)
2. Navigate to Tools & MCP → Installed MCP Server
3. Add the following to your mcp.json:

{
  "mcpServers": {
    "bitbucket-data-center-mcp": {
      "command": "npm",
      "args": ["--silent", "--prefix", "/path/to/bitbucket-data-center-mcp", "run", "dev"],
      "env": {
        "BITBUCKET_URL": "https://bitbucket.example.com",
        "BITBUCKET_TOKEN": "your-personal-access-token"
      }
    }
  }
}

Note: Replace /path/to/bitbucket-data-center-mcp with the actual path to this repository on your system.

Claude Desktop

1. Open your Claude Desktop config file:
   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
2. Add the following to the mcpServers section:

{
  "mcpServers": {
    "bitbucket-data-center-mcp": {
      "command": "npm",
      "args": ["--silent", "--prefix", "/path/to/bitbucket-data-center-mcp", "run", "dev"],
      "env": {
        "BITBUCKET_URL": "https://bitbucket.example.com",
        "BITBUCKET_TOKEN": "your-personal-access-token"
      }
    }
  }
}

Note: Replace /path/to/bitbucket-data-center-mcp with the actual path to this repository on your system.

For Developers

Scripts

Command	Description
pnpm dev	Run the MCP server
pnpm test	Run tests
pnpm typecheck	Type-check the project
pnpm inspect	Launch MCP Inspector UI

Debugging with MCP Inspector

The project includes @modelcontextprotocol/inspector as a dev dependency. Use it to interactively test tools, resources, and prompts exposed by the server.

Start the inspector:

pnpm inspect

The UI opens at http://localhost:6274.

Connect to the server in the UI:

Field	Value
Transport	STDIO
Command	tsx
Arguments	src/index.ts

Click Connect. The inspector spawns the server process and proxies the MCP protocol.

Alternatively, pass the command directly on the CLI:

npx @modelcontextprotocol/inspector tsx src/index.ts

Environment variables: Set BITBUCKET_URL and BITBUCKET_TOKEN in the Environment Variables section of the inspector UI before clicking Connect.