Atlassian Bitbucket MCP Server

This project provides a Model Context Protocol (MCP) server that acts as a bridge between AI assistants (like Anthropic's Claude, Cursor AI, or other MCP-compatible clients) and your Atlassian Bitbucket instance. It allows AI to securely access and interact with your repositories, pull requests, and workspaces in real-time.

What is MCP and Why Use This Server?

Model Context Protocol (MCP) is an open standard enabling AI models to connect securely to external tools and data sources. This server implements MCP specifically for Bitbucket Cloud.

Benefits:

• Real-time Access: Your AI assistant can directly access up-to-date Bitbucket data (repositories, PRs, etc.).
• Eliminate Copy/Paste: No need to manually transfer information between Bitbucket and your AI assistant.
• Enhanced AI Capabilities: Enables AI to analyze repositories, review pull requests, understand code context, and work directly with your version control system.
• Security: You control access via API credentials (Atlassian API Token or Bitbucket App Password). The AI interacts through the server, and sensitive operations remain contained.

Interface Philosophy: Simple Input, Rich Output

This server follows a "Minimal Interface, Maximal Detail" approach:

1. Simple Tools: Ask for only essential identifiers (like workspaceSlug, repoSlug, prId).
2. Rich Details: When you ask for a specific item (like get-repository), the server provides all relevant information by default (description, owner, links, etc.) without needing extra flags.

Available Tools

This MCP server provides the following tools for your AI assistant:

List Workspaces (list-workspaces)

Purpose: Discover available Bitbucket workspaces you have access to and find their 'slugs' (unique identifiers).

Use When: You need to know which workspaces are available or find the slug for a specific workspace to use with other tools.

Conversational Example: "Show me all my Bitbucket workspaces."

Parameter Example: {} (no parameters needed for basic list) or { query: "devteam" } (to filter).

Get Workspace (get-workspace)

Purpose: Retrieve detailed information about a specific workspace using its slug.

Use When: You know the workspace slug and need its full details or links to its contents.

Conversational Example: "Tell me more about the 'acme-corp' workspace."

Parameter Example: { workspaceSlug: "acme-corp" }

List Repositories (list-repositories)

Purpose: List repositories within a specific workspace and find their 'slugs'. Requires the workspace slug.

Use When: You need to find repositories within a known workspace or get the slug for a specific repository.

Conversational Example: "List the repositories in the 'acme-corp' workspace."

Parameter Example: { workspaceSlug: "acme-corp" } or { workspaceSlug: "acme-corp", query: "backend" } (to filter).

Get Repository (get-repository)

Purpose: Retrieve detailed information about a specific repository using its workspace and repository slugs.

Use When: You know the workspace and repository slugs and need full details like description, language, owner, etc.

Conversational Example: "Show me details for the 'backend-api' repository in the 'acme-corp' workspace."

Parameter Example: { workspaceSlug: "acme-corp", repoSlug: "backend-api" }

List Pull Requests (list-pull-requests)

Purpose: List pull requests within a specific repository. Requires workspace and repository slugs.

Use When: You need to find open/merged/etc. pull requests in a known repository or get the ID for a specific PR.

Conversational Example: "Show me the open pull requests for the 'acme-corp/frontend-app' repository."

Parameter Example: { workspaceSlug: "acme-corp", repoSlug: "frontend-app", state: "OPEN" }

Get Pull Request (get-pull-request)

Purpose: Retrieve detailed information about a specific pull request using its workspace slug, repository slug, and PR ID.

Use When: You know the identifiers for a specific PR and need its full description, reviewers, status, branches, etc.

Conversational Example: "Get the details for pull request #42 in the 'acme-corp/frontend-app' repo."

Parameter Example: { workspaceSlug: "acme-corp", repoSlug: "frontend-app", prId: "42" }

Add Pull Request Comment (add-pr-comment)

Purpose: Add comments to a pull request, including both general PR comments and inline code comments.

Use When: You need to provide feedback, ask questions, or communicate with contributors on a specific PR.

Conversational Example: "Add a comment to pull request #42 in the 'acme-corp/frontend-app' repo saying 'This looks good to merge'."

Parameter Example: { workspaceSlug: "acme-corp", repoSlug: "frontend-app", prId: "42", content: "This looks good to merge" } or with inline comment: { workspaceSlug: "acme-corp", repoSlug: "frontend-app", prId: "42", content: "Consider a constant here", inline: { path: "src/utils.js", line: 42 } }

Create Pull Request (create-pull-request)

Purpose: Create a new pull request from one branch to another within a repository.

Use When: You need to initiate a code review for a completed feature or bug fix, or want to merge changes from a feature branch into a main branch.

Conversational Example: "Create a pull request in the 'acme-corp/frontend-app' repo from the 'feature/new-login' branch to 'main' with the title 'Add new login screen'."

Parameter Example: { workspaceSlug: "acme-corp", repoSlug: "frontend-app", title: "Add new login screen", sourceBranch: "feature/new-login" }

Prerequisites

• Node.js and npm: Ensure you have Node.js (which includes npm) installed. Download from nodejs.org.
• Bitbucket Account: An active Bitbucket Cloud account with access to the workspaces and repositories you want to connect to.

Quick Start Guide

Follow these steps to connect your AI assistant to Bitbucket:

Step 1: Set Up Authentication

You have two options for authenticating with Bitbucket:

Option A: Bitbucket App Password (Recommended for Bitbucket-only use)

Important: Treat your App Password like a password. Do not share it or commit it to version control.

1. Navigate to your Bitbucket personal settings: https://bitbucket.org/account/settings/app-passwords/
2. Click Create app password.
3. Give it a Label (e.g., mcp-bitbucket-access).
4. Grant the following Permissions (at minimum):
   • Workspaces: Read
   • Repositories: Read
   • Pull requests: Read
5. Click Create.
6. Immediately copy the generated App Password. You won't be able to see it again. Store it securely.

Option B: Atlassian API Token (Use if connecting other Atlassian tools like Jira/Confluence)

Important: Treat your API token like a password.

1. Go to your Atlassian API token management page: https://id.atlassian.com/manage-profile/security/api-tokens
2. Click Create API token.
3. Give it a descriptive Label (e.g., mcp-bitbucket-access).
4. Click Create.
5. Immediately copy the generated API token. Store it securely.

Step 2: Configure the Server Credentials

Choose one of the following methods:

Method A: Global MCP Config File (Recommended)

This keeps credentials separate and organized.

1. Create the directory (if needed): ~/.mcp/

2. Create/Edit the file: ~/.mcp/configs.json

3. Add the configuration: Paste one of the following JSON structures, corresponding to your chosen authentication method, replacing the placeholders:

   Using Bitbucket App Password:

   {
   	"@aashari/mcp-server-atlassian-bitbucket": {
   		"environments": {
   			"ATLASSIAN_BITBUCKET_USERNAME": "<YOUR_BITBUCKET_USERNAME>",
   			"ATLASSIAN_BITBUCKET_APP_PASSWORD": "<YOUR_COPIED_APP_PASSWORD>"
   		}
   	}
   }
   

   • <YOUR_BITBUCKET_USERNAME>: Your Bitbucket username.
   • <YOUR_COPIED_APP_PASSWORD>: The App Password from Step 1.

   Using Atlassian API Token:

   {
   	"@aashari/mcp-server-atlassian-bitbucket": {
   		"environments": {
   			"ATLASSIAN_SITE_NAME": "<YOUR_ATLASSIAN_SITE_NAME_UNUSED_BUT_NEEDED>",
   			"ATLASSIAN_USER_EMAIL": "<YOUR_ATLASSIAN_EMAIL>",
   			"ATLASSIAN_API_TOKEN": "<YOUR_COPIED_API_TOKEN>"
   		}
   	}
   }
   

   • <YOUR_ATLASSIAN_SITE_NAME_UNUSED_BUT_NEEDED>: Enter any value (like bitbucket). This field is required by the underlying transport but not used for Bitbucket API auth when using an API token.
   • <YOUR_ATLASSIAN_EMAIL>: Your Atlassian account email.
   • <YOUR_COPIED_API_TOKEN>: The API token from Step 1.

Method B: Environment Variables (Alternative)

Set environment variables when running the server. Choose the set matching your authentication:

Using Bitbucket App Password:

ATLASSIAN_BITBUCKET_USERNAME="<YOUR_USERNAME>" \
ATLASSIAN_BITBUCKET_APP_PASSWORD="<YOUR_APP_PASSWORD>" \
npx -y @aashari/mcp-server-atlassian-bitbucket

Using Atlassian API Token:

ATLASSIAN_SITE_NAME="bitbucket" \
ATLASSIAN_USER_EMAIL="<YOUR_EMAIL>" \
ATLASSIAN_API_TOKEN="<YOUR_API_TOKEN>" \
npx -y @aashari/mcp-server-atlassian-bitbucket

Step 3: Connect Your AI Assistant

Configure your MCP client (Claude Desktop, Cursor, etc.) to run this server.

Claude Desktop

1. Open Settings (gear icon) > Edit Config.

2. Add or merge into mcpServers:

   {
   	"mcpServers": {
   		"aashari/mcp-server-atlassian-bitbucket": {
   			"command": "npx",
   			"args": ["-y", "@aashari/mcp-server-atlassian-bitbucket"]
   		}
   	}
   }
   

3. Save and Restart Claude Desktop.

4. Verify: Click the "Tools" (hammer) icon; Bitbucket tools should be listed.

Cursor AI

1. Command Palette (Cmd+Shift+P / Ctrl+Shift+P) > Cursor Settings > MCP.
2. Click + Add new MCP server.
3. Enter:
   • Name: aashari/mcp-server-atlassian-bitbucket
   • Type: command
   • Command: npx -y @aashari/mcp-server-atlassian-bitbucket
4. Click Add.
5. Verify: Wait for the indicator next to the server name to turn green.

Step 4: Using the Tools

You can now ask your AI assistant questions related to your Bitbucket instance:

• "List all the Bitbucket workspaces I have access to."
• "Show me all repositories in the 'dev-team' workspace."
• "Get information about the 'main-api' repository in the 'dev-team' workspace."
• "Show me open pull requests for the 'dev-team/main-api' repository."
• "Summarize pull request #42 in the 'dev-team/main-api' repository."
• "Create a pull request in the 'dev-team/main-api' repository from the 'feature/login' branch to 'main' with the title 'Add new login feature'."

Using as a Command-Line Tool (CLI)

You can also use this package directly from your terminal:

Quick Use with npx

No installation required - run directly using npx:

# List workspaces
npx -y @aashari/mcp-server-atlassian-bitbucket list-workspaces

# Get repository details
npx -y @aashari/mcp-server-atlassian-bitbucket get-repository --workspace my-team --repository my-api

# List pull requests
npx -y @aashari/mcp-server-atlassian-bitbucket list-pull-requests --workspace my-team --repository my-api --state OPEN

Global Installation

For frequent use, you can install the package globally on your system:

1. Install globally using npm:

   npm install -g @aashari/mcp-server-atlassian-bitbucket
   

2. Verify installation by checking the version:

   mcp-atlassian-bitbucket --version
   

3. Use the commands without npx prefix:

   # List workspaces
   mcp-atlassian-bitbucket list-workspaces
   
   # Get workspace details
   mcp-atlassian-bitbucket get-workspace --workspace my-team
   
   # List repositories in a workspace
   mcp-atlassian-bitbucket list-repositories --workspace my-team
   
   # Get repository details
   mcp-atlassian-bitbucket get-repository --workspace my-team --repository my-api
   
   # List pull requests
   mcp-atlassian-bitbucket list-pull-requests --workspace my-team --repository my-api --state OPEN
   

Configuration with Global Installation

When installed globally, you can still use the same configuration methods:

1. Using environment variables:

   # Using Bitbucket App Password
   ATLASSIAN_BITBUCKET_USERNAME="<YOUR_USERNAME>" \
   ATLASSIAN_BITBUCKET_APP_PASSWORD="<YOUR_APP_PASSWORD>" \
   mcp-atlassian-bitbucket list-workspaces
   
   # Using Atlassian API Token
   ATLASSIAN_SITE_NAME="bitbucket" \
   ATLASSIAN_USER_EMAIL="<YOUR_EMAIL>" \
   ATLASSIAN_API_TOKEN="<YOUR_API_TOKEN>" \
   mcp-atlassian-bitbucket list-workspaces
   

2. Using global MCP config file (recommended): Set up the ~/.mcp/configs.json file as described in the Quick Start Guide.

License

ISC