Bamboo MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BAMBOO_URL | Yes | URL server Bamboo (contoh: https://bamboo.bri.co.id) | |
| BAMBOO_TOKEN | No | Personal Access Token dari Bamboo | |
| BAMBOO_PASSWORD | No | Password (alternatif token) | |
| BAMBOO_USERNAME | No | Username (alternatif token) | |
| BAMBOO_SSL_VERIFY | No | Set false untuk skip SSL verification | true |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List all Bamboo projects. Returns a list of projects with their keys and names. |
| list_plansA | List build plans, optionally filtered by project key. Args: project_key: Optional project key to filter plans (e.g., 'PROJ') |
| get_planB | Get detailed information about a specific build plan. Args: plan_key: The plan key (e.g., 'PROJ-PLAN') |
| get_plan_branchesA | List all branches of a build plan. Args: plan_key: The plan key (e.g., 'PROJ-PLAN') |
| 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 |
| get_build_resultB | Get the result of a specific build. Args: build_key: The build result key (e.g., 'PROJ-PLAN-123') |
| 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 |
| 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 |
| stop_buildB | Stop a running build. Args: build_key: The build result key to stop (e.g., 'PROJ-PLAN-123') |
| list_deployment_projectsB | List all deployment projects in Bamboo. |
| get_deployment_projectC | Get details of a specific deployment project. Args: deployment_project_id: The deployment project ID |
| 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) |
| 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 |
| create_projectA | Create a new Bamboo project. Args: key: Project key (uppercase letters, e.g., 'MYPROJ') name: Project name description: Optional project description |
| 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 |
| get_plan_variablesB | Get variables defined for a build plan. Args: plan_key: The plan key (e.g., 'PROJ-PLAN') |
| 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 |
| 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']) |
| 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 |
| get_queue_statusA | Get the current build queue status. Shows builds currently queued and currently building. |
| list_agentsA | List all Bamboo build agents and their status. |
| get_server_infoA | Get Bamboo server information including version. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mvadly/bamboo-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server