Official server by Buildkite
Buildkite MCP server
Read Buildkite pipelines, builds, jobs, logs and test results.
Install
Pick your agent and copy one line. Remote servers ask you to sign in on first use.
claude mcp add buildkite -e BUILDKITE_API_TOKEN=YOUR_VALUE -- docker run -i --rm -e BUILDKITE_API_TOKEN ghcr.io/buildkite/buildkite-mcp-server:0.7.0
# ~/.codex/config.toml [mcp_servers.buildkite] command = "docker" args = ["run", "-i", "--rm", "-e", "BUILDKITE_API_TOKEN", "ghcr.io/buildkite/buildkite-mcp-server:0.7.0"] [mcp_servers.buildkite.env] BUILDKITE_API_TOKEN = "<your BUILDKITE_API_TOKEN>"
gemini mcp add -e BUILDKITE_API_TOKEN=YOUR_VALUE buildkite docker run -i --rm -e BUILDKITE_API_TOKEN ghcr.io/buildkite/buildkite-mcp-server:0.7.0
{
"mcpServers": {
"buildkite": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"BUILDKITE_API_TOKEN",
"ghcr.io/buildkite/buildkite-mcp-server:0.7.0"
],
"env": {
"BUILDKITE_API_TOKEN": "<your BUILDKITE_API_TOKEN>"
}
}
}
}code --add-mcp '{"name":"buildkite","command":"docker","args":["run","-i","--rm","-e","BUILDKITE_API_TOKEN","ghcr.io/buildkite/buildkite-mcp-server:0.7.0"],"env":{"BUILDKITE_API_TOKEN":"<your BUILDKITE_API_TOKEN>"}}'What it can do
From Buildkite's own MCP documentation.
Sign in
Remote: OAuth (access tokens last 12 hours, refresh tokens 7 days), or API token pass-through at /direct with Authorization: Bearer. Local: BUILDKITE_API_TOKEN.
Tools
current_useruser_token_organizationaccess_tokenlist_clustersget_clusterlist_pipelinesget_pipelinecreate_pipelineupdate_pipelinelist_buildsget_buildcreate_buildcancel_buildrebuild_buildwait_for_buildlist_jobsget_jobretry_jobunblock_jobget_build_failure_summarycompare_buildssearch_logstail_logsread_logslist_annotations
Options
- Read-only endpoint: https://mcp.buildkite.com/mcp/readonly, or the X-Buildkite-Readonly: true header with /direct.
- One toolset via URL: /x/{toolset}, for example /mcp/x/builds/readonly.
- Several toolsets via the X-Buildkite-Toolsets header, for example user,pipelines,builds.
- Toolsets: user, clusters, cluster_secrets, cache_registries, agents, pipelines, builds, investigations, logs, artifacts, annotations, tests.
- ?organization=<slug> preselects an organization during OAuth.
- Headless agents use https://mcp.buildkite.com/direct with an API token.
Good to know
- Remote server limit is 50 requests per minute per user, separate from your org REST API limit.
- Under active development. Tools can change or be removed. For a fixed version, run the local server from a versioned Docker tag or release binary.
- Orgs with an API IP allowlist must add Buildkite's egress IPs.
- Read-only MCP does not stop an agent from using other credentials, such as the bk CLI.
- wait_for_build checks for up to 45 seconds per call.
Details
- Registry name
- io.github.buildkite/buildkite-mcp-server
- Latest version
- 0.7.0 (updated 2025-10-10)
- Packages
ghcr.io/buildkite/buildkite-mcp-server:0.7.0 (oci)
- Links
- Buildkite docsSource
More in Developer tools
Reviewed Oct 21, 2026. Official means published under Buildkite's namespace in the MCP registry. It is not a security audit.
Built an MCP server? Get it listed everywhere →
Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →