Buildkite

Official Buildkite Developer tools

Lets an agent inspect Buildkite pipelines, builds, jobs and tests, compare builds, and retry jobs. Summary written by AI Index.

The registry’s description: MCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors.

Local package (oci) Needs a key: BUILDKITE_API_TOKEN

Add to your client

Add the Buildkite MCP server to Claude Code

  1. Run the command

    claude mcp add -e BUILDKITE_API_TOKEN=<BUILDKITE_API_TOKEN> buildkite -- docker run -i --rm run BUILDKITE_API_TOKEN ghcr.io/buildkite/buildkite-mcp-server:0.7.0 ghcr.io/buildkite/buildkite-mcp-server:0.7.0
  2. Fill in the values ↓

  3. Check it’s connected

If the file already has servers, add the entry inside the existing object. To check it’s connected, restart or reload the client and look for buildkite in its list of MCP servers. A server that needs sign-in opens it on first use.

What you fill in

Required values appear as <NAME> placeholders in the snippets; add optional ones the same way. Descriptions are the server’s registry entry’s.

  • <BUILDKITE_API_TOKEN> Environment variable Required · Secret

    Buildkite API token for authentication. Get one from https://buildkite.com/user/api-access-tokens

Client compatibility

By transport: whether the client’s docs list a transport this server offers. It doesn’t cover sign-in or other requirements.

Sources

This data comes from the Official MCP Registry.