Buildkite MCP Server

@Drew-Goddyn

About Buildkite MCP Server

A Model Context Protocol (MCP) server for Buildkite integration

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "buildkite": {
      "command": "npx",
      "args": [
        "-y",
        "@drew-goddyn/buildkite-mcp"
      ],
      "env": {
        "BUILDKITE_ACCESS_TOKEN": "your-buildkite-access-token"
      }
    }
  }
}

Tools

No tools detected

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Buildkite MCP Server?

A microservice that retrieves information from Buildkite via the Model Context Protocol (MCP), enabling AI assistants and MCP-compatible tools (e.g., Cursor) to query Buildkite pipelines, builds, jobs, and logs.

How to use Buildkite MCP Server?

Clone the repo, run npm install, set the BUILDKITE_ACCESS_TOKEN environment variable, and start the server with node index.js. Alternatively, configure it in Cursor’s ~/.cursor/config/mcp.json using the npx command, and Cursor will manage the lifecycle automatically.

Key features of Buildkite MCP Server

List organizations, pipelines, and builds
Get build details with job information
List all jobs or only failed jobs in a build
Retrieve job logs and spec failures
Retry failed jobs directly from the server
List pipeline build failures with failed job URLs

Use cases of Buildkite MCP Server

Debugging CI/CD failures by querying build logs and failed spec details
Automating build inspection and retry workflows from AI assistants
Aggregating pipeline failure history for analysis
Integrating Buildkite data into MCP‑powered development tools like Cursor

FAQ from Buildkite MCP Server

What environment variable is required?

The BUILDKITE_ACCESS_TOKEN environment variable must be set to a Buildkite API token with at least read access.

How do I start the server?

You can run it manually with node index.js (optionally specifying PORT), or let Cursor start it automatically by configuring the npx command in mcp.json.

What MCP endpoints are available?

The server provides endpoints for listing organizations, pipelines, builds, jobs, failed jobs, job spec failures, job logs, and pipeline build failures, as well as retrying jobs and listing failed specs from a build URL.

What HTTP errors can the server return?

It returns 400 for missing/invalid parameters, 401 for invalid tokens, 404 for missing resources, and 500 for internal errors.

What is the default port?

The server runs on port 63330 unless overridden by the PORT environment variable.

Frequently asked questions

What environment variable is required?

The `BUILDKITE_ACCESS_TOKEN` environment variable must be set to a Buildkite API token with at least read access.

How do I start the server?

You can run it manually with `node index.js` (optionally specifying `PORT`), or let Cursor start it automatically by configuring the `npx` command in `mcp.json`.