Atlassian Bamboo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BAMBOO_URL | Yes | Base URL of your Bamboo server | |
| BAMBOO_PROXY | No | Proxy URL (e.g., http://proxy:8080) | |
| BAMBOO_TOKEN | Yes | Personal access token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bamboo_server_infoA | Get Bamboo server information including version, edition, and state |
| bamboo_health_checkB | Check Bamboo server health status |
| bamboo_list_projectsB | List all Bamboo projects |
| bamboo_get_projectA | Get details of a specific Bamboo project by key |
| bamboo_list_plansC | List all Bamboo build plans |
| bamboo_get_planB | Get details of a specific Bamboo build plan by key |
| bamboo_search_plansB | Search for Bamboo build plans by name |
| bamboo_enable_planB | Enable a Bamboo build plan |
| bamboo_disable_planC | Disable a Bamboo build plan |
| bamboo_clone_planB | Clone an existing Bamboo build plan to a new plan |
| bamboo_list_plan_branchesB | List all branches for a Bamboo build plan |
| bamboo_get_plan_branchB | Get details of a specific plan branch |
| bamboo_trigger_buildC | Trigger a build for a Bamboo plan |
| bamboo_stop_buildB | Stop a running build for a Bamboo plan |
| bamboo_get_build_resultC | Get the result of a specific build |
| bamboo_get_latest_resultB | Get the latest build result for a plan |
| bamboo_list_build_resultsC | List build results with optional filters |
| bamboo_get_build_logsC | Get the build logs for a specific build. Returns log file URLs that can be accessed via browser. |
| bamboo_get_build_result_logsA | Get build result with actual log content. For plan builds, fetches logs from all jobs. For job builds, returns logs directly. |
| bamboo_get_build_queueB | Get the current Bamboo build queue |
| bamboo_get_deployment_queueA | Get the current Bamboo deployment queue |
| bamboo_list_deployment_projectsA | List all Bamboo deployment projects |
| bamboo_get_deployment_projectA | Get details of a specific deployment project |
| bamboo_create_deployment_projectB | Create a new Bamboo deployment project linked to a build plan |
| bamboo_trigger_deploymentC | Trigger a deployment to an environment |
| bamboo_get_deployment_resultsC | Get deployment results for an environment |
| bamboo_get_deployment_resultA | Get a specific deployment result with optional logs |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 27 tools
Most tools have distinct purposes, but bamboo_get_build_logs and bamboo_get_build_result_logs could cause confusion as both relate to logs. The descriptions help disambiguate (URLs vs actual content), but the overlap is slight.
All tools follow a consistent 'bamboo_verb_noun' pattern in snake_case, making it predictable and easy to understand the action and resource.
27 tools is on the high side but still justifiable given the broad scope of Bamboo (projects, plans, branches, builds, deployments, server info). Each tool contributes to a complete CI/CD workflow.
The toolset covers many operations but lacks a create plan from scratch (only clone) and update plan functionality. Core workflows like triggering and viewing results are covered, but some lifecycle gaps exist.