Skip to content
AgentAtlas

Buildkite · Codex

Add the Buildkite MCP server to Codex

Read Buildkite pipelines, builds, jobs, logs and test results.

Official serverLocalDeveloper tools

1. Add the server

Run in your terminal

# ~/.codex/config.toml
[mcp_servers.buildkite]
command = "docker"
args = ["run", "-i", "--rm", "-e", "BUILDKITE_API_TOKEN", "ghcr.io/buildkite/buildkite-mcp-server:0.7.0"]

[mcp_servers.buildkite.env]
BUILDKITE_API_TOKEN = "<your BUILDKITE_API_TOKEN>"

Scopes, env vars, OAuth and limits: Codex MCP config guide

2. Sign in

Run codex mcp login <name> to complete OAuth for a remote server. Buildkite runs locally and needs BUILDKITE_API_TOKEN. Replace the placeholder values above with your own before starting Codex.

3. Try it

Ask Codex for something Buildkite can do. Read Buildkite pipelines, builds, jobs, logs and test results. Approve the first tool call and check the result before allowing write actions automatically.

  • · Each server is a [mcp_servers.<name>] table in config.toml.
  • · Use enabled_tools or disabled_tools to keep the tool list short.

FAQ

How do I add the Buildkite MCP server to Codex?
Run: # ~/.codex/config.toml …. Run codex mcp login <name> to complete OAuth for a remote server.
Is this the official Buildkite MCP server?
Yes. It is published by Buildkite as io.github.buildkite/buildkite-mcp-server in the official MCP registry.
Does the Buildkite MCP server need an API key?
Yes. It runs locally and requires BUILDKITE_API_TOKEN.

Links

Buildkite in other clients

More developer tools for Codex

Built an MCP server? Get it listed everywhere →

Shipping an Android app? Google Play needs 12 testers for 14 days first. Get them with Tester Exchange →

Reviewed Oct 21, 2026. Command generated from the registry record and checked against Codex's documented syntax.