Skip to main content
Glama
ATERCATES

Bitbucket MCP Server

by ATERCATES
README.md
# Bitbucket MCP Server

A Model Context Protocol (MCP) server for integrating with Bitbucket Cloud and Server APIs. This MCP server enables AI assistants like Claude and Cursor to interact with your Bitbucket repositories, pull requests, pipelines, and other resources.

[![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
[![npm version](https://img.shields.io/npm/v/@atercates/bitbucket-mcp.svg)](https://www.npmjs.com/package/@atercates/bitbucket-mcp)

## Features

โœจ **Comprehensive Bitbucket Integration** - 59 tools covering repositories, PRs, branches, commits, pipelines, and more

๐Ÿ”’ **Secure Authentication** - App password tokens or basic auth with granular permission control via Bitbucket

๐Ÿ“ **Well-Documented** - Complete API reference, architecture guides, and deployment instructions in `/docs`

๐Ÿงช **Fully Tested** - Comprehensive unit test suite with full tool coverage (Vitest)

โšก **Modular Design** - Clean, maintainable architecture organized by feature domain (11 handler modules)

๐Ÿ›ก๏ธ **Safety First** - 3 operation modes (readonly, safe, full) with fine-grained tool control

๐Ÿš€ **Production Ready** - Built with pnpm, ESLint, Prettier, and modern TypeScript

## Quick Start

### Installation

```bash
# Option 1: Global install
pnpm add -g @atercates/bitbucket-mcp

# Option 2: Use with NPX (no installation required)
npx -y @atercates/bitbucket-mcp@latest

# Option 3: Local development
git clone https://github.com/ATERCATES/bitbucket-mcp.git
cd bitbucket-mcp
pnpm install
pnpm build
pnpm start
```

### Configuration

**REQUIRED Environment Variables:**

```bash
# Authentication (Personal API Token ONLY)
export BITBUCKET_USERNAME="user@example.com"    # Your Atlassian email address
export BITBUCKET_API_TOKEN="ATBBxxxxxxxxxxxxx"  # Personal API Token (starts with ATBB or ATATT)

# Default Workspace (optional but recommended)
export BITBUCKET_WORKSPACE="my-workspace"       # Your default workspace name
```

**Optional Configuration:**

```bash
# Server Operation Mode
export BITBUCKET_MODE="safe"  # readonly | safe (default) | full

# Fine-grained tool control
export BITBUCKET_ENABLED_TOOLS="getPullRequest,listPullRequests,createPullRequest"
export BITBUCKET_DISABLED_TOOLS="deleteBranch,deleteRepository"

# Custom API URL (for self-hosted Bitbucket Server)
export BITBUCKET_URL="https://bitbucket.company.com/rest/api/2.0"
```

**๐Ÿ” Operation Modes:**

- **`readonly`** - Only GET operations (no modifications)
- **`safe`** - GET + POST/PUT operations, but no deletes (default)
- **`full`** - All operations including dangerous deletes

**โš ๏ธ Authentication Notes:**
- This MCP server strictly enforces **Personal API Tokens** (starting with `ATBB` or `ATATT`)
- App Passwords and Access Tokens (BBAT-xxx) are **NOT supported**
- `BITBUCKET_USERNAME` must be your Atlassian email address

### Running the Server

```bash
# If installed globally
bitbucket-mcp

# If using NPX
npx -y @atercates/bitbucket-mcp@latest

# If installed locally
pnpm start
```

The server will start and listen for MCP protocol connections via stdio.

## Integration with MCP Clients

### Claude / Cursor Configuration

Add to your MCP configuration (`.mcp.json` or similar):

```json
{
  "mcpServers": {
    "bitbucket": {
      "command": "bitbucket-mcp",
      "env": {
        "BITBUCKET_USERNAME": "user@example.com",
        "BITBUCKET_API_TOKEN": "ATBBxxxxxxxxxxxxx",
        "BITBUCKET_WORKSPACE": "my-workspace",
        "BITBUCKET_MODE": "safe"
      }
    }
  }
}
```

**Examples:**

```json
// Read-only mode (safe for production analysis)
{
  "BITBUCKET_MODE": "readonly"
}

// Safe mode (default - no deletes)
{
  "BITBUCKET_MODE": "safe"
}

// Full mode (all operations including deletes)
{
  "BITBUCKET_MODE": "full"
}

// Fine-grained control (only specific tools)
{
  "BITBUCKET_ENABLED_TOOLS": "getPullRequest,listPullRequests,getPullRequestDiff"
}

// Blacklist specific tools
{
  "BITBUCKET_DISABLED_TOOLS": "deleteBranch,deleteRepository,deleteTag"
}
```

Or with npx:

```json
{
  "mcpServers": {
    "bitbucket": {
      "command": "npx",
      "args": ["-y", "@atercates/bitbucket-mcp@latest"],
      "env": {
        "BITBUCKET_USERNAME": "user@example.com",
        "BITBUCKET_API_TOKEN": "ATBBxxxxxxxxxxxxx",
        "BITBUCKET_WORKSPACE": "my-workspace",
        "BITBUCKET_MODE": "safe"
      }
    }
  }
}
```

## Available Tools

The server provides 59 tools organized into 11 categories:

| Category | Tools |
|----------|-------|
| **Repositories** | List, get, create repositories |
| **Pull Requests** | Create, approve, merge, decline PRs |
| **PR Comments** | Create, delete PR comments |
| **PR Tasks** | Create, update, delete PR tasks (TODOs) |
| **PR Content** | Get diffs and commits |
| **Branches & Tags** | List, create, delete branches and tags |
| **Commits** | List commits and commit details |
| **Pipelines** | List, run, stop pipeline runs |
| **Source Code** | Read file content from repositories |
| **Users** | Get current user and workspace info |
| **Branching Model** | Get branching strategy configuration |

**Complete reference:** See [docs/TOOLS.md](docs/TOOLS.md)

## Environment Variables

### Authentication (Required)

- `BITBUCKET_USERNAME` - Your Atlassian email address (e.g., `user@example.com`)
- `BITBUCKET_API_TOKEN` - Personal API Token starting with `ATBB-` or `ATATT-`

**How to create:**
1. Go to https://bitbucket.org/account/settings/app-passwords/
2. Click "Create API token"
3. Select permissions: Repositories (Read, Write), Pull requests (Read, Write), Pipelines (Read)
4. Copy the generated token
5. Set expiration date (max 1 year)

### Configuration (Optional)

- `BITBUCKET_WORKSPACE` - Default workspace name (can be provided per-tool call)
- `BITBUCKET_URL` - API base URL (default: `https://api.bitbucket.org/2.0`)
- `BITBUCKET_MODE` - Operation mode: `readonly`, `safe` (default), or `full`
- `BITBUCKET_ENABLED_TOOLS` - Comma-separated list of tools to enable (whitelist mode)
- `BITBUCKET_DISABLED_TOOLS` - Comma-separated list of tools to disable (blacklist mode)

### Logging (Optional)

- `BITBUCKET_LOG_DISABLE` - Disable file logging (default: `false`)
- `BITBUCKET_LOG_FILE` - Custom log file path
- `BITBUCKET_LOG_DIR` - Custom log directory
- `BITBUCKET_LOG_PER_CWD` - Create per-directory logs (default: `false`)

## Documentation

- **[Tools Reference](docs/TOOLS.md)** - Complete API documentation for all 59 tools with examples
- **[Architecture Guide](docs/architecture/ARCHITECTURE.md)** - Technical design, modular structure, and extension guide

## Development

### Prerequisites

- Node.js 24
- pnpm (or npm)

### Setup

```bash
git clone https://github.com/ATERCATES/bitbucket-mcp.git
cd bitbucket-mcp
pnpm install
```

### Build

```bash
pnpm build          # Compile TypeScript
pnpm lint           # Run ESLint  
pnpm format         # Format with Prettier
pnpm format:check   # Check formatting
```

### Testing

```bash
pnpm test           # Run Vitest suite
pnpm test:watch     # Watch mode
```

### Running in Development

```bash
pnpm dev            # Run with tsx (watch mode, no build required)
# OR
pnpm build && pnpm start
```

### MCP Inspector (Debugging)

```bash
pnpm inspector      # Launch interactive MCP inspector to test tools
```

## Project Structure

```
src/
โ”œโ”€ index.ts              # Entry point
โ”œโ”€ server.ts             # MCP server orchestration
โ”œโ”€ client.ts             # Bitbucket API client
โ”œโ”€ config.ts             # Configuration management
โ”œโ”€ logger.ts             # File-based logging
โ”œโ”€ types.ts              # TypeScript definitions
โ”œโ”€ schemas.ts            # JSON schemas
โ”œโ”€ utils.ts              # Utilities
โ”œโ”€ pagination.ts         # Pagination helper
โ””โ”€ handlers/             # Feature modules
   โ”œโ”€ repositories.ts
   โ”œโ”€ pull-requests.ts
   โ”œโ”€ pr-comments.ts
   โ”œโ”€ pr-tasks.ts
   โ”œโ”€ pr-content.ts
   โ”œโ”€ refs.ts
   โ”œโ”€ commits.ts
   โ”œโ”€ pipelines.ts
   โ”œโ”€ source.ts
   โ”œโ”€ users.ts
   โ”œโ”€ branching-model.ts
   โ””โ”€ index.ts

docs/
โ”œโ”€ TOOLS.md              # Tools reference
โ””โ”€ architecture/
   โ””โ”€ ARCHITECTURE.md    # Technical design

__tests__/
โ”œโ”€ test-utils.ts         # Test helpers
โ””โ”€ handlers/             # Handler tests
```

## Architecture

The server uses a modular handler-based architecture:

```
MCP Client โ†’ Server โ†’ Handler Modules โ†’ BitbucketClient โ†’ Bitbucket API
```

Each handler module:
- Defines tools (names, schemas, descriptions)
- Implements handlers (async functions)
- Can mark tools as dangerous
- Is automatically registered by the server

See [docs/architecture/ARCHITECTURE.md](docs/architecture/ARCHITECTURE.md) for details.

## Dangerous Operations

Some tools that perform destructive operations are marked as dangerous:

- `deletePullRequestComment`
- `deletePullRequestTask`
- `deleteBranch`
- `deleteTag`

These require `BITBUCKET_MODE=full` to use, preventing accidental data loss.

## Troubleshooting

### Authentication Issues

**Test your credentials:**
```bash
# Test Personal API Token
curl -u "user@example.com:ATBBxxxxxx" \
  https://api.bitbucket.org/2.0/user

# Should return your user info if credentials are valid
```

**Common errors:**

1. **"BITBUCKET_USERNAME is required"**
   - Set `BITBUCKET_USERNAME` to your Atlassian email address.

2. **"BITBUCKET_API_TOKEN is required"**
   - Set `BITBUCKET_API_TOKEN` to your Personal API Token (starts with ATBB).

3. **"Invalid token format"**
   - The token must start with `ATBB`. App passwords and Access Tokens are not supported.

4. **"401 Unauthorized"**
   - Check username/token are correct
   - Verify token hasn't expired (max 1 year)
   - Ensure you are using your **email address** as username

### View Logs

**macOS:**
```bash
tail -f ~/Library/Logs/bitbucket-mcp/bitbucket.log
```

**Linux:**
```bash
tail -f ~/.local/state/bitbucket-mcp/bitbucket.log
```

**Windows:**
```bash
Get-Content -Path "$env:LOCALAPPDATA\bitbucket-mcp\bitbucket.log" -Tail 50 -Wait
```

### Self-Hosted Bitbucket

For self-hosted Bitbucket Server, set the API URL:

```bash
BITBUCKET_URL=https://bitbucket.mycompany.com/rest/api/2.0 bitbucket-mcp
```

## License

MIT License - See [LICENSE](LICENSE) file for details.

## Support

- ๐Ÿ”ง Check [docs/TOOLS.md](docs/TOOLS.md) for tool documentation with examples
- ๐Ÿ—๏ธ Review [docs/architecture/ARCHITECTURE.md](docs/architecture/ARCHITECTURE.md) for technical details
- ๐Ÿ› Enable logging with `BITBUCKET_LOG_DISABLE=false` for debugging
- ๐Ÿž Report issues at https://github.com/ATERCATES/bitbucket-mcp/issues

---

**Architecture:** Modular handler-based design with 11 feature modules  
**Test Framework:** Vitest  
**Package Manager:** pnpm

TDQS

C2.9/5.0

Scored across 59 tools

Disambiguation3/5

Most tools are cleanly separated by resource and action, but the five branching-model tools (project vs repository, model vs settings vs effective) have overlapping descriptions that an agent would struggle to distinguish. Comments, tasks, and PR review actions are otherwise fairly unambiguous.

Naming Consistency3/5

The majority of tools follow a get/list/create/update/action + resource pattern, making the set mostly predictable. However, convertTodraft, getPendingReviewPRs, resolveComment/reopenComment, and the snake_case bitbucket_api_request break the convention.

Tool Count2/5

With 59 tools the server is substantially over the practical MCP threshold; even though each tool maps to a distinct API operation, the volume is heavy for an agent to scan and select from. Some closely related branching-model and comment tools could be consolidated.

Completeness3/5

The pull request lifecycle is very complete, and pipelines, branches, tags, commits, and comments have solid coverage for common tasks. However, repository mutation is absent and delete operations are missing for branches, tags, comments, and tasks, while the generic fallback is GET-only, so these gaps cannot be worked around.

Maintenance

ActivitySlowing
ResponsivenessNo issues