Bitbucket MCP Servers

This repository contains Model Context Protocol (MCP) server implementations for Bitbucket Cloud integration.

MCP Tools are available for Bitbucket operations, including:

• list_pull_open_requests: Gets all open pull requests in a Bitbucket repository.
• get_pull_request_comments: Gets comments for a specific pull request.
• get_pull_request_details: Gets detailed information about a pull request including description, metadata, and changed files.

Projects

• BitbucketRemoteMcpServer: ASP.NET Web API-based MCP server for server-based installations (Streamable HTTP or SSE transport)
• BitbucketMcpServer: Console-based MCP server for local workstation installations (stdio transport)

Running via Docker & Linux Server (Recommended)

1. From your Linux server, create a directory for your configuration:

   mkdir -p /opt/bitbucket-mcp-server
   cd /opt/bitbucket-mcp-server
   

2. Pull the Docker image:

   docker pull peakflames/bitbucket-remote-mcp-server
   

3. Create an appsettings.json file tailored to your Bitbucket configuration:

   {
     "BitbucketCloudConfig": {
       "AccountName": "your-workspace-name"
     }
   }
   

4. Run the Docker container with your chosen authentication method:

   Using OAuth 2.0 (Recommended):

   docker run -d \
     --name bitbucket-mcp-server \
     -p 8080:8080 \
     -e BITBUCKET_MCP_CONSUMER_KEY="your_consumer_key" \
     -e BITBUCKET_MCP_SECRET_KEY="your_secret_key" \
     -v $(pwd)/appsettings.json:/app/appsettings.json \
     peakflames/bitbucket-remote-mcp-server
   

   Using Basic Authentication:

   docker run -d \
     --name bitbucket-mcp-server \
     -p 8080:8080 \
     -e BITBUCKET_MCP_USERNAME="your_bitbucket_username" \
     -e BITBUCKET_MCP_API_TOKEN="your_bitbucket_app_password" \
     -v $(pwd)/appsettings.json:/app/appsettings.json \
     peakflames/bitbucket-remote-mcp-server
   

5. The server should now be running. MCP clients will connect using:

   • Streamable HTTP Transport: http://{{your-server-ip}}:8080/
   • SSE Transport: http://{{your-server-ip}}:8080/sse

Configuration Options (appsettings.json)

The server uses appsettings.json for configuration with a single set of credentials that can access any repository in your Bitbucket account.

| Setting | Description | Required | Default | |---------|-------------|----------|---------| | AccountName | The Bitbucket workspace/account name | Yes | N/A |

Note: Authentication credentials (either OAuth 2.0 or Basic Auth) are retrieved from environment variables at startup (see Environment Variables section below).

Environment Variables

The server supports two authentication methods: OAuth 2.0 Client Credentials and Basic Authentication. You must configure one of these methods using environment variables.

OAuth 2.0 Client Credentials (Recommended for Production)

OAuth 2.0 provides more secure authentication for server-to-server communication and is recommended for production deployments.

Linux/macOS:

export BITBUCKET_MCP_CONSUMER_KEY="your_consumer_key"
export BITBUCKET_MCP_SECRET_KEY="your_secret_key"

Windows (PowerShell):

$env:BITBUCKET_MCP_CONSUMER_KEY = "your_consumer_key"
$env:BITBUCKET_MCP_SECRET_KEY = "your_secret_key"

Windows (Command Prompt):

set BITBUCKET_MCP_CONSUMER_KEY=your_consumer_key
set BITBUCKET_MCP_SECRET_KEY=your_secret_key

How to obtain OAuth 2.0 credentials:

1. Log in to your Bitbucket workspace
2. Navigate to Settings > OAuth consumers
3. Click Add consumer
4. Configure the consumer with the necessary permissions (e.g., repositories read/write, pull requests)
5. Save and note your Consumer Key and Consumer Secret

Basic Authentication (Alternative Method)

Basic authentication uses your Bitbucket username and app password. This method is simpler to

... View full README on GitHub