Exposes Buildkite data including pipelines, builds, jobs, and test results, allowing AI tools to interact with Buildkite CI/CD infrastructure. Provides tools for managing clusters, queues, pipelines, builds, artifacts, annotations, and test executions.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@buildkite-mcp-servershow me the status of the main pipeline"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
buildkite-mcp-server
Full documentation is available at buildkite.com/docs/apis/mcp-server.
Experimental: Tool Search
When using many MCP tools, context usage can become significant. The --dynamic-toolsets flag enables Anthropic's Tool Search pattern which marks most tools for on-demand loading.
To use this feature:
Start the server with the
--dynamic-toolsetsflag:buildkite-mcp-server stdio --dynamic-toolsetsEnable tool search in Claude Code by setting the environment variable:
export ENABLE_TOOL_SEARCH=true
With both enabled, tools will be loaded on-demand rather than all at once, significantly reducing context usage. Use the list_toolsets tool to browse available categories and search_tools to discover specific tools.
Note: This feature requires Claude Code support for the defer_loading hint. See claude-code#12836 for details.
Related MCP server: Burpsuite MCP Server
Library Usage
The exported Go API of this module should be considered unstable, and subject to breaking changes as we evolve this project.
Security
To ensure the MCP server is run in a secure environment, we recommend running it in a container.
This image is built from cgr.dev/chainguard/static and runs as an unprivileged user.
Contributing
Development guidelines are in DEVELOPMENT.md.
License
MIT © Buildkite
SPDX-License-Identifier: MIT