Atlassian Bamboo MCP Server

A Model Context Protocol (MCP) server that brings Atlassian Bamboo CI/CD operations directly into AI assistants like Claude Code and Cursor.

❌ Without Bamboo MCP

Working with Bamboo CI/CD requires constant context switching:

• ❌ Switching to browser to check build status
• ❌ Manually navigating through Bamboo UI to find logs
• ❌ Copy-pasting build keys and deployment IDs
• ❌ No AI assistance for CI/CD troubleshooting

✅ With Bamboo MCP

Bamboo MCP brings your CI/CD operations directly into your AI workflow:

What's the status of the latest build for project MY-PROJECT?

Show me the deployment logs for deployment result 2661941325

Trigger a build for plan PROJ-PLAN with variable ENV=staging

No tab-switching, no manual navigation — just ask and get instant CI/CD insights.

Features

• 26 tools covering all major Bamboo operations
• Build logs with actual content (not just URLs)
• Deployment logs with full output
• Proxy support for corporate environments
• TypeScript with full type safety

Installation

Prerequisites

• Node.js 18+
• Bamboo personal access token (how to create)

From Source

git clone https://github.com/norus/atlassian-bamboo-mcp.git
cd atlassian-bamboo-mcp
npm install
npm run build

From npm

npm install -g bamboo-mcp-server

Configuration

The server requires these environment variables:

Creating a Bamboo Token

1. Log into Bamboo
2. Go to Profile → Personal access tokens
3. Click Create token
4. Give it a name and appropriate permissions
5. Copy the token (you won't see it again)

Setup

Run this command:

claude mcp add bamboo -- npx -y bamboo-mcp-server@latest

Or add to ~/.claude/settings.json:

{
  "mcpServers": {
    "bamboo": {
      "command": "npx",
      "args": ["-y", "bamboo-mcp-server@latest"],
      "env": {
        "BAMBOO_URL": "https://bamboo.example.com",
        "BAMBOO_TOKEN": "your-token"
      }
    }
  }
}

Add to your config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "bamboo": {
      "command": "npx",
      "args": ["-y", "bamboo-mcp-server@latest"],
      "env": {
        "BAMBOO_URL": "https://bamboo.example.com",
        "BAMBOO_TOKEN": "your-token",
        "BAMBOO_PROXY": "http://proxy:8080"
      }
    }
  }
}

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bamboo": {
      "command": "npx",
      "args": ["-y", "bamboo-mcp-server@latest"],
      "env": {
        "BAMBOO_URL": "https://bamboo.example.com",
        "BAMBOO_TOKEN": "your-token"
      }
    }
  }
}

BAMBOO_URL="https://bamboo.example.com" \
BAMBOO_TOKEN="your-token" \
npx bamboo-mcp-server

Build the image

docker build -t bamboo-mcp-server .

Run with Docker

docker run -i --rm \
  -e BAMBOO_URL="https://bamboo.example.com" \
  -e BAMBOO_TOKEN="your-token" \
  -e BAMBOO_PROXY="http://host.docker.internal:8080" \
  bamboo-mcp-server

Proxy configuration

When using a proxy from Docker:

• macOS/Windows: Use host.docker.internal to reach the host (e.g., http://host.docker.internal:8080)
• Linux: Use --network host flag or the host's actual IP address

Use with Claude Desktop

{
  "mcpServers": {
    "bamboo": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "BAMBOO_URL=https://bamboo.example.com",
        "-e", "BAMBOO_TOKEN=your-token",
        "-e", "BAMBOO_PROXY=http://host.docker.internal:8080",
        "bamboo-mcp-server"
      ]
    }
  }
}

Docker Compose

services:
  bamboo-mcp:
    build: .
    environment:
      - BAMBOO_URL=https://bamboo.example.com
      - BAMBOO_TOKEN=${BAMBOO_TOKEN}
      - BAMBOO_PROXY=http://host.docker.internal:8080
    stdin_open: true

Available Tools

Server (2)

Projects (2)

Plans (6)

Branches (2)

Builds (7)

Queue (2)

Deployments (6)

Example Prompts

Show me all failed builds in the last 24 hours

What's blocking the deployment queue?

Get the logs for build PROJ-PLAN-123 and tell me why it failed

Trigger a build for MY-PROJECT with variable DEPLOY_ENV=staging

List all branches for plan MY-PLAN and their build status

Development

# Install dependencies
npm install

# Build
npm run build

# Run tests
npm test

# Run tests with coverage
npm run test:coverage

# Run locally
BAMBOO_URL="https://bamboo.example.com" \
BAMBOO_TOKEN="your-token" \
node dist/index.js

Troubleshooting

• Verify BAMBOO_URL is correct and accessible
• If behind a proxy, set BAMBOO_PROXY
• Check if your token has expired

• Verify your BAMBOO_TOKEN is correct
• Ensure the token hasn't expired
• Check token permissions in Bamboo

• Restart Claude Code/Desktop after config changes
• Verify the path to dist/index.js is absolute
• Check Claude's MCP logs for errors

Security

• No hardcoded secrets — all credentials via environment variables
• Input validation — Zod schemas on all tool inputs
• Proxy support — works in corporate environments
• Read-heavy — most operations are read-only

For security issues, please report via GitHub Security tab.

License

MIT

Contributing

Contributions welcome! Please read our contributing guidelines before submitting PRs.