Buildkite MCP Server

MIT

buildkiteci-cdpipelinesdevopsobservability

Summary

Buildkite's official MCP server: query pipelines, builds, jobs, logs, test runs and flaky-test data from an agent, over a hosted OAuth endpoint or a self-run binary.

Features

Read pipelines, builds, jobs, job logs and test runs from a Buildkite organisation
Hosted endpoint with OAuth, plus a token-passthrough and a read-only variant
Self-hostable single Go binary and a hardened Chainguard container image
Access is governed by Buildkite API token scopes, so read-only really is read-only
Configurable API origin and HTTP header passthrough for self-hosted deployments

Installation

Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.

Any MCP-compatible agent

Most agents (Claude, Cursor, Windsurf, VS Code, and more) read a standard mcpServers configuration.

Open your agent's MCP configuration file.
Merge the snippet below into it, filling in the environment variables with your own values.
Restart the agent — the "Buildkite MCP Server" tools will be available.

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

Claude Code

Add the server with a single CLI command.

claude mcp add buildkite-mcp-server -e BUILDKITE_API_TOKEN=bkua_your_token -- docker run -i --rm -e BUILDKITE_API_TOKEN ghcr.io/buildkite/buildkite-mcp-server stdio

Claude Desktop

Add the server to claude_desktop_config.json (Settings → Developer → Edit Config).

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

Self-hosted native binary over stdio

{
  "command": "buildkite-mcp-server",
  "args": [
    "stdio"
  ],
  "env": {
    "BUILDKITE_API_TOKEN": "bkua_your_token"
  }
}

Buildkite-hosted read-only endpoint (OAuth in the browser)

{
  "command": "npx",
  "args": [
    "-y",
    "mcp-remote",
    "https://mcp.buildkite.com/mcp/readonly"
  ]
}

Description

The Buildkite MCP Server exposes a Buildkite organisation's CI data to any MCP client. Instead of tailing a job log in a browser tab, you ask the agent why the last build on main failed and it reads the pipeline, the build, the failing job and that job's log itself.

Two ways to run it

Hosted. Buildkite operates the server, so there is nothing to install:

https://mcp.buildkite.com/mcp — OAuth. Access tokens last 12 hours, refresh tokens seven days.
https://mcp.buildkite.com/direct — pass your own Buildkite API token through instead of doing the OAuth dance.
https://mcp.buildkite.com/mcp/readonly — the same server restricted to tools whose required scope starts with read_. The obvious default for an agent you do not want triggering builds.

The hosted endpoints have their own rate-limit quota, separate from your REST API allowance.

Self-hosted. A single Go binary, also published as a Chainguard-based container image that runs as an unprivileged user. Configure it with BUILDKITE_API_TOKEN, optionally BUILDKITE_BASE_URL to point at a different API origin, and BUILDKITE_PASSTHROUGH_HTTP_HEADERS when running in HTTP mode and you need specific headers forwarded. Self-hosted requests count against your organisation's normal REST API rate limit.

What actually gates access

Tool calls succeed or fail on the scopes of the token behind them, not on the server. A token with only read scopes gives you an inspection-only assistant no matter which endpoint you point it at — which is the recommended starting posture, and why the read-only URL exists.

MIT licensed, written in Go, and maintained by Buildkite in the open.

Related MCP Servers

MCP: Resend

by Resend

New

Resend's official MCP server for transactional and marketing email — send, schedule and batch messages, manage templates, contacts, broadcasts, automations, domains and suppressions from an agent.

Developer Tools

MCP: Postman MCP Server

by Postman

New

Postman's official MCP server — reach your workspaces, collections, specs and environments from Claude Code, Cursor, VS Code or Copilot, in four tool tiers.

Developer Tools

MCP: Jupyter MCP Server

by Datalayer

New

Drive live Jupyter notebooks from an agent — read and edit cells, execute code, see rich outputs, and run against local JupyterLab or a cloud sandbox.

Developer Tools

MCP: deja-vu

by Vladislav Shulcz

New

Indexes the coding-agent sessions already sitting on your disk — months of history from before you installed it — and serves them back over MCP. 3.5 GB searched in ~1.5 ms, no LLM, no embeddings.

Developer ToolsDatabases & Data

Browse all MCP servers →