Skip to main content
Glama
Sign In
Bamboo MCP Server

Bamboo MCP Server

by mvadly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Bamboo MCP Server

MCP Server untuk manajemen CI/CD Pipeline Atlassian Bamboo dari Kiro IDE.

Setup

1. Install di WSL

# Masuk ke WSL
wsl

# Install package ke virtual environment
cd /home/mvadly
source .venv/bin/activate
pip install /mnt/c/Users/90150244/mcp-servers/bamboo-mcp

2. Konfigurasi MCP di Kiro

Tambahkan entry berikut ke file ~/.kiro/settings/mcp.json (di bagian mcpServers):

"bamboo": {
  "command": "wsl",
  "args": [
    "bash",
    "-c",
    "BAMBOO_URL=https://bamboo.bri.co.id BAMBOO_TOKEN=YOUR_BAMBOO_TOKEN_HERE BAMBOO_SSL_VERIFY=false /home/mvadly/.venv/bin/python -m bamboo_mcp.server"
  ]
}

3. Environment Variables

Variable

Keterangan

Required

BAMBOO_URL

URL server Bamboo (contoh: https://bamboo.bri.co.id)

Ya

BAMBOO_TOKEN

Personal Access Token dari Bamboo

Ya*

BAMBOO_USERNAME

Username (alternatif token)

Ya*

BAMBOO_PASSWORD

Password (alternatif token)

Ya*

BAMBOO_SSL_VERIFY

Set false untuk skip SSL verification

Tidak

*Gunakan BAMBOO_TOKEN ATAU kombinasi BAMBOO_USERNAME/BAMBOO_PASSWORD.

4. Mendapatkan Bamboo Token

  1. Login ke Bamboo

  2. Klik profile icon > Manage account

  3. Pilih Personal access tokens

  4. Klik Create token

  5. Beri nama dan permissions yang diperlukan

  6. Copy token dan paste di konfigurasi

Related MCP server: Jenkins MCP Server

Tools yang Tersedia

Project & Plan Management

  • list_projects - List semua project

  • list_plans - List build plans (bisa filter per project)

  • get_plan - Detail plan tertentu

  • get_plan_branches - List branches dari plan

  • create_project - Buat project baru

  • enable_plan - Enable/disable plan

  • get_plan_variables - Lihat variabel plan

  • set_plan_variable - Set variabel plan

Build Management

  • trigger_build - Trigger build baru (bisa pilih branch & variabel)

  • get_build_result - Lihat hasil build

  • list_build_results - List history build

  • get_build_log - Lihat build log

  • stop_build - Stop build yang sedang berjalan

Deployment Management

  • list_deployment_projects - List deployment projects

  • get_deployment_project - Detail deployment project

  • trigger_deployment - Deploy ke environment tertentu

  • get_deployment_result - Lihat status deployment

Pipeline Generation

  • create_bamboo_specs_yaml - Generate bamboo-specs YAML pipeline

  • create_bamboo_specs_java - Generate Bamboo Specs Java configuration

Queue & Agents

  • get_queue_status - Status antrian build

  • list_agents - List build agents

Server

  • get_server_info - Informasi server Bamboo

Contoh Penggunaan

Setelah MCP terhubung, Anda bisa meminta Kiro:

  • "List semua plans di project PAYROLL"

  • "Trigger build untuk PAYROLL-CONV di branch feature/new-format"

  • "Cek status build terakhir PAYROLL-CONV"

  • "Buatkan pipeline CI/CD untuk project Go dengan Docker"

  • "Deploy versi terbaru ke environment SIT"

  • "Lihat log build yang gagal"

Available Tools

22 tools
create_bamboo_specs_javaA

Generate Bamboo Specs Java configuration for a CI/CD pipeline.

Creates a PlanSpec.java file for Bamboo Specs that defines the complete pipeline.

Args: project_key: The Bamboo project key (e.g., 'PROJ') plan_name: Display name for the plan plan_key: Short key for the plan (e.g., 'BUILD') repository_url: Git repository URL branch: Default branch to build (default: 'master') build_commands: List of build commands to execute docker_image: Optional Docker image for build agent deployment_environments: Optional list of deployment environment names

Inputs: plan_key (required), plan_name (required), project_key (required), repository_url (required), +4 more. Returns: result

create_bamboo_specs_yamlA

Generate a bamboo-specs YAML pipeline configuration file.

Creates a complete bamboo-specs/bamboo.yaml that defines CI/CD pipeline. This file can be committed to the repository to configure the plan via Bamboo Specs.

Args: project_key: The Bamboo project key (e.g., 'PROJ') plan_name: Display name for the plan plan_key: Short key for the plan (e.g., 'BUILD') repository_url: Git repository URL branch: Default branch to build (default: 'master') build_commands: List of build commands to execute docker_image: Optional Docker image for build agent deployment_environments: Optional list of deployment environment names (e.g., ['DEV', 'SIT', 'UAT', 'PROD'])

Inputs: plan_key (required), plan_name (required), project_key (required), repository_url (required), +4 more. Returns: result

create_projectA

Create a new Bamboo project.

Args: key: Project key (uppercase letters, e.g., 'MYPROJ') name: Project name description: Optional project description

Inputs: key (required), name (required), description. Returns: result

enable_planB

Enable or disable a build plan.

Args: plan_key: The plan key (e.g., 'PROJ-PLAN') enabled: True to enable, False to disable

Inputs: plan_key (required), enabled. Returns: result

get_build_logB

Get build logs for a specific build result.

Args: build_key: The build result key (e.g., 'PROJ-PLAN-123') job_key: Optional specific job key within the build

Inputs: build_key (required), job_key. Returns: result

get_build_resultB

Get the result of a specific build.

Args: build_key: The build result key (e.g., 'PROJ-PLAN-123')

Inputs: build_key (required). Returns: result

get_deployment_projectC

Get details of a specific deployment project.

Args: deployment_project_id: The deployment project ID

Inputs: deployment_project_id (required). Returns: result

get_deployment_resultC

Get the latest deployment result for an environment.

Args: deployment_project_id: The deployment project ID environment_id: The environment ID to check

Inputs: environment_id (required), deployment_project_id (required). Returns: result

get_planB

Get detailed information about a specific build plan.

Args: plan_key: The plan key (e.g., 'PROJ-PLAN')

Inputs: plan_key (required). Returns: result

get_plan_branchesA

List all branches of a build plan.

Args: plan_key: The plan key (e.g., 'PROJ-PLAN')

Inputs: plan_key (required). Returns: result

get_plan_variablesB

Get variables defined for a build plan.

Args: plan_key: The plan key (e.g., 'PROJ-PLAN')

Inputs: plan_key (required). Returns: result

get_queue_statusA

Get the current build queue status.

Shows builds currently queued and currently building.

Inputs: no named parameters. Returns: result

get_server_infoA

Get Bamboo server information including version.

Inputs: no named parameters. Returns: result

list_agentsA

List all Bamboo build agents and their status.

Inputs: no named parameters. Returns: result

list_build_resultsB

List recent build results for a plan.

Args: plan_key: The plan key (e.g., 'PROJ-PLAN') max_results: Maximum number of results to return (default: 10) include_all_states: Include in-progress and queued builds

Inputs: plan_key (required), max_results, include_all_states. Returns: result

list_deployment_projectsB

List all deployment projects in Bamboo.

Inputs: no named parameters. Returns: result

list_plansA

List build plans, optionally filtered by project key.

Args: project_key: Optional project key to filter plans (e.g., 'PROJ')

Inputs: project_key. Returns: result

list_projectsA

List all Bamboo projects.

Returns a list of projects with their keys and names.

Inputs: no named parameters. Returns: result

set_plan_variableB

Create or update a plan variable.

Args: plan_key: The plan key (e.g., 'PROJ-PLAN') variable_name: Variable name variable_value: Variable value

Inputs: plan_key (required), variable_name (required), variable_value (required). Returns: result

stop_buildB

Stop a running build.

Args: build_key: The build result key to stop (e.g., 'PROJ-PLAN-123')

Inputs: build_key (required). Returns: result

trigger_buildA

Trigger a new build for a plan.

Args: plan_key: The plan key (e.g., 'PROJ-PLAN') branch: Optional branch name to build variables: Optional dict of build variables to override

Inputs: plan_key (required), branch, variables. Returns: result

trigger_deploymentB

Trigger a deployment to a specific environment.

Args: deployment_project_id: The deployment project ID environment_id: The target environment ID version_name: Optional release version name to create build_result_key: Optional build result key to deploy (uses latest if not specified)

Inputs: environment_id (required), deployment_project_id (required), version_name, build_result_key. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.5/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, with clear boundaries between listing and getting details. There is slight overlap between the two create_bamboo_specs tools (YAML vs Java), but descriptions clarify the difference, so ambiguity is minimal.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern (e.g., list_projects, get_plan, trigger_build). Verbs like list, get, create, set, trigger are used predictably, and nouns align with domain concepts, making the set easy to navigate.

    Tool Count5/5

    22 tools cover the main aspects of Bamboo CI/CD (projects, plans, builds, deployments, agents, server info, and configuration generation) without redundancy. Each tool serves a distinct purpose, and the count feels appropriate for the domain.

    Completeness3/5

    Notable gaps exist: there is no create_plan tool (only config generation), no delete or update for projects/plans/deployments, and no list environments for deployments. These gaps limit full lifecycle management, though core monitoring and triggering operations are covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • TeamCity MCP Server

      Daghis
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding assistants to interact with JetBrains TeamCity CI/CD server through natural language commands. Supports triggering builds, monitoring status, analyzing test failures, and managing build configurations directly from development environments.
      32
      2,848 npm
      32
      MIT

    • Atlassian Bamboo MCP Server

      norus
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to interact with Atlassian Bamboo CI/CD, allowing natural language queries to check build status, fetch logs, trigger builds, and manage deployments.
      27
      305 npm
      6
      MIT