Add the Buildkite MCP server to VS Code (GitHub Copilot)

code --add-mcp '{"name":"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: VS Code (GitHub Copilot) MCP config guide

VS Code opens the sign-in flow when Copilot first calls a remote OAuth server. Buildkite runs locally and needs BUILDKITE_API_TOKEN. Replace the placeholder values above with your own before starting VS Code (GitHub Copilot).

Ask VS Code (GitHub Copilot) 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.

• · mcp.json uses a top-level servers key, not mcpServers.
• · code --add-mcp installs a server into your user profile from the terminal.

How do I add the Buildkite MCP server to VS Code (GitHub Copilot)?

Run: code --add-mcp '{"name":"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>"}}'. VS Code opens the sign-in flow when Copilot first calls a remote OAuth 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.