MCP Server

io.github.buildkite/buildkite-mcp-server

developer-tools

MCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors.

Install

Paste into claude_desktop_config.json:

{
  "mcpServers": {
    "buildkite-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/buildkite/buildkite-mcp-server:0.7.0"
      ],
      "env": {
        "BUILDKITE_API_TOKEN": "<BUILDKITE_API_TOKEN>"
      }
    }
  }
}

Run in a terminal:

claude mcp add buildkite-mcp-server --env BUILDKITE_API_TOKEN=<BUILDKITE_API_TOKEN> -- docker run -i --rm ghcr.io/buildkite/buildkite-mcp-server:0.7.0

Paste into .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{
  "mcpServers": {
    "buildkite-mcp-server": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/buildkite/buildkite-mcp-server:0.7.0"
      ],
      "env": {
        "BUILDKITE_API_TOKEN": "<BUILDKITE_API_TOKEN>"
      }
    }
  }
}

Transport & auth

Transport: stdio - Runs locally over stdio. Your client launches the process itself; you need the matching runtime installed (Node for npx, uv for uvx, Docker for docker run).

Auth: requires credentials - replace the <PLACEHOLDER> environment values in the config with your own keys (see the vendor's docs).

Links

Source repository

Skip the install — WingMan's own 271 tools run hosted, no setup: browse the hosted tool directory. One endpoint, one free key: https://wingmanprotocol.com/mcp.