buildkite

This MCP server exposes Buildkite data (pipelines, builds, jobs, and tests) to AI tools and editors via the MCP protocol. You can start the server in a container, enabling optional dynamic tool loading to minimize context usage. Tools available through the server include category-based toolsets for navigating pipelines, including search capabilities to discover specific tools. When dynamic toolsets are enabled, tools are loaded on-demand to optimize memory and performance, which is beneficial for setups with many tools or limited resources.

To use the server, run it in a container and connect your MCP-enabled tooling to the server's endpoint. If you enable the dynamic toolsets feature, ensure Claude Code (or your MCP client) supports the defer_loading hint and set the ENABLE_TOOL_SEARCH environment variable to true to enable on-demand loading of tools. You can browse available categories with list_toolsets and search for specific tools with search_tools once the server is running.

Prerequisites:

• Docker (or another container runtime) installed on your host
• Access to Buildkite API data (credentials may be required depending on your Buildkite setup)

Install and run:

1. Install Docker if you don't have it:

   • macOS: install Docker Desktop from https://www.docker.com/products/docker-desktop
   • Windows: install Docker Desktop from https://www.docker.com/products/docker-desktop
   • Linux: follow your distro's instructions to install the docker package and start the daemon

2. Pull or build the MCP server image:

   • If you have a prebuilt image: docker pull buildkite-mcp-server:latest
   • If you build locally: docker build -t buildkite-mcp-server:latest .

3. Run the MCP server:

   • docker run -i buildkite-mcp-server:latest

4. Verify the server is reachable via its MCP endpoint (the exact URL/port depends on the image and configuration). Consult the server's documentation for the default port and authentication requirements.

Optional: If you plan to use dynamic toolsets, ensure your MCP client supports defer_loading and set ENABLE_TOOL_SEARCH=true in the environment when starting the client or container.

Notes and tips:

• The server is intended to be run in a secure, containerized environment as recommended in the Security section.
• If you enable dynamic toolsets, tools will be loaded on demand rather than all at once, reducing context usage. This requires client support for the defer_loading hint (see Claude Code issue linked in the README).
• Environment variable ENABLE_TOOL_SEARCH can be used to toggle tool search capabilities on the client side when using dynamic toolsets.
• The Go API of this module is considered unstable and may undergo breaking changes as the project evolves.
• If you encounter connection or authentication issues, ensure network access to your Buildkite data source and verify any required API credentials or tokens are correctly configured in your environment.