# Buildkite MCP server > Inspect Buildkite pipelines, builds, jobs, logs and test analytics, and compare builds to find what changed. - Listing: https://mcp.tc/i/buildkite - Connect: use the server's own URL `https://mcp.buildkite.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint. - Type: remote (Streamable HTTP) - Auth: OAuth sign-in - Category: [Cloud & DevOps](https://mcp.tc/c/cloud-devops) - Vendor: Buildkite - Homepage: - Repository: - Package: oci `ghcr.io/buildkite/buildkite-mcp-server` ## About Connects an AI assistant to Buildkite CI/CD data. It exposes pipelines, builds, jobs, job logs and test analytics, so you can investigate failing builds, read log output and compare a build against an earlier passing one with the read-only compare\_builds tool. The hosted endpoint is https://mcp.buildkite.com/mcp and uses OAuth sign-in. A read-only endpoint is available at https://mcp.buildkite.com/mcp/readonly. A local alternative runs as the Docker image ghcr.io/buildkite/buildkite-mcp-server and needs a Buildkite API token in BUILDKITE\_API\_TOKEN. ## What it can do - Browse Buildkite pipelines, builds and jobs - Read and tail job logs - Summarize build failures - Compare a build with an earlier passing baseline - Query test analytics data - Use a read-only endpoint for safer access ## Example prompts - "Why did build 1234 on the main pipeline fail?" - "What changed since this build last passed on main?" - "Show the last log lines for the failing job in my latest build." - "List recent builds for the deploy pipeline." ## Install ### Claude Code 1. Run this in a terminal, in your project folder: ```bash claude mcp add --transport http buildkite https://mcp.buildkite.com/mcp ``` 2. Start Claude Code, type `/mcp`, pick **buildkite** and choose **Authenticate**. A browser window opens for the Buildkite sign-in. Add `--scope user` to make it available in every project, not just this one. ### Claude Desktop 1. Open **Settings → Connectors** and click **Add custom connector**. 2. Name it **Buildkite** and paste this URL: ```url https://mcp.buildkite.com/mcp ``` 3. Click **Add**, then **Connect**, and sign in when Buildkite asks. Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too. ### claude.ai 1. Open the connector form on claude.ai. This button fills in the name and URL for you: [Add to claude.ai]() (opens connector settings) 2. Check that the URL reads `https://mcp.buildkite.com/mcp` and click **Add**. 3. Click **Connect** and sign in when Buildkite asks. Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**. ### ChatGPT 1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**. 2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server. 3. Paste `https://mcp.buildkite.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Buildkite to sign in. Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts. ### Cursor [Add to Cursor]() (opens Cursor) Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project): `mcp.json`: ```json { "mcpServers": { "buildkite": { "url": "https://mcp.buildkite.com/mcp" } } } ``` Cursor shows **Needs login** next to the server. Click it to sign in. ### VS Code [Install in VS Code]() (opens VS Code) Or from a terminal: ```bash code --add-mcp '{"name":"buildkite","type":"http","url":"https://mcp.buildkite.com/mcp"}' ``` Or commit it to the repo in `.vscode/mcp.json`: `.vscode/mcp.json`: ```json { "servers": { "buildkite": { "type": "http", "url": "https://mcp.buildkite.com/mcp" } } } ``` VS Code asks you to sign in the first time the server starts. ### Devin Desktop 1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows): `mcp_config.json`: ```json { "mcpServers": { "buildkite": { "serverUrl": "https://mcp.buildkite.com/mcp" } } } ``` 2. Refresh the MCP server list in Cascade and sign in when asked. Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers. ### Codex ```bash codex mcp add buildkite --url https://mcp.buildkite.com/mcp codex mcp login buildkite ``` Or edit `~/.codex/config.toml` directly: `config.toml`: ```toml [mcp_servers.buildkite] url = "https://mcp.buildkite.com/mcp" ``` ### Gemini CLI ```bash gemini mcp add --transport http buildkite https://mcp.buildkite.com/mcp ``` Then, inside Gemini CLI, run `/mcp auth buildkite` to sign in. This adds it to the current project. Add `-s user` to use it everywhere. ### Any client Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file. ```json { "mcpServers": { "buildkite": { "type": "http", "url": "https://mcp.buildkite.com/mcp" } } } ``` Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE. Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.buildkite.com/mcp`. ## Details - Server version: 0.7.0 - Last checked: 2026-10-03 (reachable, asks for credentials) - Listed: 2026-10-03 - Updated: 2026-10-03 --- Source: https://mcp.tc/i/buildkite (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report