Skip to main content
Watch: I Built an AI App Without Leaving Databricks

CI/CD and testing - official Buildkite server

Buildkite MCP server

Open source MCP server, offered as a Buildkite-hosted remote endpoint or a local binary/container, that exposes Buildkite Pipelines and Test Engine data so an agent can inspect pipelines, builds, jobs, logs, artifacts and tests and, with write access, trigger, retry or unblock builds. Buildkite hosts it at https://mcp.buildkite.com/mcp, or you can run buildkite/mcp-server (docker) locally with OAuth or API key auth.

Last verified 15 tools7 sources

Install

Terminal
claude mcp add --transport http buildkite https://mcp.buildkite.com/mcp

VS Code

JSON
{
  "servers": {
    "buildkite": {
      "url": "https://mcp.buildkite.com/mcp",
      "type": "http"
    }
  }
}

Generic

JSON
{
  "mcpServers": {
    "buildkite": {
      "url": "https://mcp.buildkite.com/mcp"
    }
  }
}

Tools

list_pipelines
Lists all pipelines in an organization with basic details, build counts and current status.
get_pipeline
Retrieves a pipeline's configuration, steps, environment variables and build statistics.
create_pipeline
Creates a new YAML pipeline with repository connection and cluster assignment.
list_builds
Lists lightweight build summaries for an organization or a pipeline.
get_build
Retrieves metadata for a specific build.
create_build
Triggers a new build for a commit and branch.
cancel_build
Cancels a running build.
list_jobs
Lists jobs for a build with optional state filtering.
retry_job
Retries a job that failed or timed out.
unblock_job
Unblocks a blocked job so the build can continue.
search_logs
Searches job log entries using regex patterns with optional context lines.
tail_logs
Shows the last N entries from a job log.
list_artifacts_for_build
Lists a build's artifacts across all its jobs.
list_tests
Lists tests in a Test Engine suite with aggregated execution metrics.
get_failed_executions
Retrieves failed test executions for a Test Engine run, optionally with full error details.

As documented on October 17, 2026. A running server reports its current list through tools/list.

Notes and caveats

  • Remote endpoints: OAuth at /mcp (recommended, tokens valid 12 hours), read-only at /mcp/readonly, API token pass-through for headless agents at https://mcp.buildkite.com/direct (Bearer bkua_ token), and per-toolset paths such as /mcp/x/pipelines.
  • Remote requests have their own rate limit (50 requests per minute per user on the direct endpoint).
  • Organizations with an API IP allowlist must allow Buildkite egress IPs.
  • Buildkite says the server is under active development and tools may change, including breaking changes; pin a local Docker tag or release binary for stable behavior.
  • Cursor install is via the Buildkite plugin on the Cursor Marketplace or a deep link.
  • The local server needs a Buildkite API access token.
  • Latest release v1.28.0 (2026-10-13).
  • Vendor docs carry no beta label.

FAQ

What does the Buildkite MCP server do?

Open source MCP server, offered as a Buildkite-hosted remote endpoint or a local binary/container, that exposes Buildkite Pipelines and Test Engine data so an agent can inspect pipelines, builds, jobs, logs, artifacts and tests and, with write access, trigger, retry or unblock builds. The vendor documents 15 tools, including list_pipelines, get_pipeline, create_pipeline and list_builds.

How do I add the Buildkite MCP server to Claude Code?

Run claude mcp add --transport http buildkite https://mcp.buildkite.com/mcp, copied from Buildkite's docs. This page also has snippets for VS Code and Generic.

Does the Buildkite MCP server need authentication?

Yes, OAuth or API key. Transport: Streamable HTTP, stdio, SSE. Status: GA, last checked October 17, 2026.

Sources

Last verified against 7 Buildkite pages, then re-checked independently.

Newsletter

New MCP servers, the week they ship

One email per week. New official MCP servers, the coding tools that support them and how developers wire them up.