← Explore all mcp servers

DEVELOPMENT WORKFLOW / Buildkite

Buildkite MCP server

Exposes Buildkite pipelines, builds, jobs, and tests to an MCP client, locally or through Buildkite's remote server.

“Model Context Protocol (MCP) server exposing Buildkite data (pipelines, builds, jobs, tests) to AI tooling and editors.”

01 / THE REASONING

Why this made the selection.

  • The repository README at this commit says the server exposes Buildkite pipelines, builds, jobs, and tests.
  • Buildkite's local install page documents a Docker command, and the commit's LICENSE is MIT, Copyright (c) 2025 Buildkite.
  • The pinned README exposes Buildkite pipelines, builds, jobs, and tests, and it documents compare_builds as a read-only comparison.
  • HTTP mode can forward only headers the operator names, and a per-request Authorization mode will not fall back to a shared token.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md at e437254055c32fea1c461c861ec47f7e36bdf1e6
  • LICENSE at the same commit
  • https://buildkite.com/docs/apis/mcp-server/local/installing.md
  • README.md
  • LICENSE

Our findings

  • Minimum token scopes do not include build logs or artifacts; those require read_build_logs and read_artifacts separately.
  • Secret-detail reads return metadata rather than secret values; write_secrets is a separate grant.
  • The installation guide offers a 1Password reference mechanism, which requires an authenticated op CLI.
  • MCP lane cross-review matched the retained primary setup/permission evidence and the added source-specific findings before this wave was frozen.
  • The server exposes Buildkite pipelines, builds, jobs, and tests. compare_builds is read-only: it picks an earlier passing build on the same branch and does not change Buildkite state.
  • HTTP passthrough forwards only headers the operator listed, and only to the Buildkite origin. If Authorization is the per-request credential, a missing header is HTTP 401 and the server never falls back to a shared token.
  • That header passthrough is not available in stdio mode. Baseline search stops at 500 candidates, and a build with more than 1,000 jobs returns an error instead of a partial inventory.

Not established by this review

  • No server installation, authentication, live API operation or isolation test was performed.
  • The server was not started and its tools were not called.
  • A pin does not verify transitive dependencies.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

docker run --pull=always -q -it --rm -e BUILDKITE_API_TOKEN=<api-token-value> buildkite/mcp-server stdio

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Replace <api-token-value> with a token that has only the scopes you intend. The command was not run.
  2. Prefer the remote server only if you accept that its endpoint is not pinned to this reviewed commit.

Before you start

  • Docker 20 or later for that command
  • A Buildkite API access token

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "buildkite": {
      "command": "docker",
      "args": [
        "run",
        "--pull=always",
        "-q",
        "-i",
        "--rm",
        "-e",
        "BUILDKITE_API_TOKEN",
        "buildkite/mcp-server",
        "stdio"
      ],
      "env": {
        "BUILDKITE_API_TOKEN": "bkua_xxxxx"
      }
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Buildkite MCP README ↗Checked

    https://github.com/buildkite/buildkite-mcp-server/blob/e437254055c32fea1c461c861ec47f7e36bdf1e6/README.md

    Supports: Server purpose, MIT notice

  2. https://buildkite.com/docs/apis/mcp-server/local/installing.md

    Supports: Docker install command, Token scope names

  3. Buildkite MCP LICENSE ↗Checked

    https://github.com/buildkite/buildkite-mcp-server/blob/e437254055c32fea1c461c861ec47f7e36bdf1e6/LICENSE

    Supports: MIT License, Copyright (c) 2025 Buildkite

  4. Buildkite MCP README ↗Checked

    https://github.com/buildkite/buildkite-mcp-server/blob/e437254055c32fea1c461c861ec47f7e36bdf1e6/README.md

    Supports: Server purpose, MIT notice

  5. https://buildkite.com/docs/apis/mcp-server/local/installing.md

    Supports: Docker install command, Token scope names

Evidence & Ask