Add the Buildkite MCP server to Gemini CLI

gemini mcp add -e BUILDKITE_API_TOKEN=YOUR_VALUE buildkite docker run -i --rm -e BUILDKITE_API_TOKEN ghcr.io/buildkite/buildkite-mcp-server:0.7.0

Scopes, env vars, OAuth and limits: Gemini CLI MCP config guide

Run /mcp auth <name> inside Gemini CLI to sign in to an OAuth server. Buildkite runs locally and needs BUILDKITE_API_TOKEN. Replace the placeholder values above with your own before starting Gemini CLI.

Ask Gemini CLI 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.

• · In settings.json, streamable HTTP servers use httpUrl, SSE servers use url, local servers use command.
• · includeTools and excludeTools limit which tools the model sees.

How do I add the Buildkite MCP server to Gemini CLI?

Run: gemini mcp add -e BUILDKITE_API_TOKEN=YOUR_VALUE buildkite docker run -i --rm -e BUILDKITE_API_TOKEN ghcr.io/buildkite/buildkite-mcp-server:0.7.0. Run /mcp auth <name> inside Gemini CLI to sign in to an 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.