Buildkite MCP Server README
The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Buildkite MCP Server listing page.
buildkite-mcp-server
Model Context Protocol (MCP) server exposing Buildkite data (pipelines, builds, jobs, tests) to AI tooling and editors.
Full documentation is available at buildkite.com/docs/apis/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.
Passing identity headers through HTTP mode
Self-hosted HTTP deployments can forward selected headers from each inbound MCP request to the Buildkite API:
Repeat --passthrough-http-header to allow more than one header, or set a comma-separated BUILDKITE_PASSTHROUGH_HTTP_HEADERS value. Only explicitly allowed headers are forwarded, and only to the origin configured by BUILDKITE_BASE_URL. They are removed from requests redirected elsewhere.
To authenticate each MCP request with its own Buildkite API token, allow Authorization and omit the process-wide token:
In this mode every /mcp request must contain exactly one non-empty Authorization header. Missing credentials return HTTP 401; the server never falls back to a shared API token. The reverse proxy in front of the MCP server is responsible for authenticating callers and setting or validating any forwarded identity headers.
Header passthrough is not available in stdio mode. Before serving job logs, the server verifies that the current caller can access the job log. This check is performed for every log-tool request, including when the log data is already cached.
Contributing
Development guidelines are in DEVELOPMENT.md.
License
MIT © Buildkite
SPDX-License-Identifier: MIT