Developer · Local MCP server
Buildkite MCP Server
MCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.buildkite/buildkite-mcp-server- Version
- 0.7.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2025-10-10
- Updated
- 2025-10-10
- Publisher
- buildkite (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/buildkite) · how
- Repository
- github.com/buildkite/buildkite-mcp-server
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker)runtime: docker | ghcr.io/buildkite/buildkite-mcp-server:0.7.0 | - | stdio |
How to connect Buildkite MCP Server
Buildkite MCP Server runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/buildkite/buildkite-mcp-server:0.7.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e BUILDKITE_API_TOKEN ghcr.io/buildkite/buildkite-mcp-server:0.7.0. It reads the environment variable BUILDKITE_API_TOKEN (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"buildkite-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"BUILDKITE_API_TOKEN",
"ghcr.io/buildkite/buildkite-mcp-server:0.7.0"
],
"env": {
"BUILDKITE_API_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Bugherd MCPBugHerd API v2 integration - 37 tools for projects, tasks, comments, and webhooks. | Local · stdio |
| BugProofCapture, replay, and debug failures with portable, executable bug artifacts. | Local · stdio |
| BuildStart a NorthernGo cloud build from Cursor, Claude or Codex. EU database included. | Remote · HTTPLive check: sign-in required |
| BuilderforceRun tickets, boards, OKRs and cloud coding agents in your Builderforce workspace. | Remote · HTTPLive check: sign-in required |
| BuildPulseBuildPulse CI test analytics for AI agents - flaky tests, CI failures, flakiness, and code coverage. | Remote & Local · HTTP, stdioLive check: sign-in required |
| BuildtreeUpload Android and iOS builds to buildtree and get install links, QR codes and tester feedback. | Local · stdio |
| Buildutilities MCPDeterministic dev utilities: UUIDs, hashes, encoding, JWT, cron, regex. No network, no API key. | Local · stdio |
| Bulk Sender Lint21 dated checks over SPF, DKIM, DMARC, RFC 8058 one-click unsubscribe and TLS, in VS Code and in the. | Local · stdio |