BitbucketMcpServers

Bitbucket MCP Servers implements MCP tools to interact with Bitbucket Cloud. The server exposes capabilities for listing open pull requests, retrieving pull request comments, and obtaining detailed pull request information, including descriptions, metadata, and changed files. You can run the remote MCP server via Docker and connect clients using either the Streamable HTTP transport or SSE transport. To use the server, deploy the container with your preferred authentication method (OAuth 2.0 or Basic Auth) and point your MCP clients to the appropriate transport URL (http://<server-ip>:8080/ for Streamable HTTP or http://<server-ip>:8080/sse for SSE). The tools will accept repository identifiers and perform Bitbucket API calls under the configured credentials.

Prerequisites:

• Docker installed on your server or host machine.
• Access to Bitbucket Cloud and the ability to create OAuth 2.0 credentials or an app password.

Installation steps:

1. Prepare a deployment directory (optional): mkdir -p /opt/bitbucket-mcp-server cd /opt/bitbucket-mcp-server

2. Pull and run the Docker image: docker pull peakflames/bitbucket-remote-mcp-server docker run -d
   --name bitbucket-mcp-server
   -p 8080:8080
   peakflames/bitbucket-remote-mcp-server

3. Configure authentication credentials via environment variables at startup or in a mounted config:

   • OAuth 2.0 (recommended): set BITBUCKET_MCP_CONSUMER_KEY and BITBUCKET_MCP_SECRET_KEY
   • Basic authentication: set BITBUCKET_MCP_USERNAME and BITBUCKET_MCP_API_TOKEN

4. Create appsettings.json (optional for Bitbucket AccountName configuration) and mount into container if needed, e.g.: { "BitbucketCloudConfig": { "AccountName": "your-workspace-name" } } Then mount to /app/appsettings.json inside the container as per your deployment method.

5. Verify the server is running and reachable at:

   • Streamable HTTP: http://<server-ip>:8080/
   • SSE: http://<server-ip>:8080/sse

Notes:

• The server auto-detects the authentication method based on environment variables: OAuth 2.0 if both consumer key and secret are set; Basic Auth if username and app password are set. Do not mix credentials from both methods.
• Ensure the Bitbucket AccountName in appsettings.json matches a workspace you own or have access to.
• When using Docker, you may want to mount a local appsettings.json to /app/appsettings.json inside the container to provide the AccountName configuration.
• If you encounter authentication issues, double-check that the OAuth consumer is active and has the required scopes, or that the app password has necessary repository permissions.
• Tools available: list_pull_open_requests, get_pull_request_comments, get_pull_request_details.
• The MCP client configuration in your environment should point to the server URL with the appropriate transport (streamable HTTP or SSE).