Add the Buildkite MCP server to Cursor

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

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

Cursor prompts you to sign in the first time a remote OAuth server is used. Buildkite runs locally and needs BUILDKITE_API_TOKEN. Replace the placeholder values above with your own before starting Cursor.

Ask Cursor 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.

• · Remote servers take a url; local servers take command and args.
• · Values can reference ${env:NAME} so secrets stay out of the file.

How do I add the Buildkite MCP server to Cursor?

Run: { …. Cursor prompts you to sign in the first time a remote OAuth server is used.

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.