Buildkite is a DevOps MCP server that lets Claude Code, Cursor, Windsurf and any MCP-compatible AI agent manage Buildkite pipelines and builds. Install in 1 minute with mcpizy install buildkite.
DevOps
Manage Buildkite pipelines and builds. Monitor CI/CD status and trigger deployments.
mcpizy install buildkitenpx -y @buildkite/mcp-serverMCP server for Azure DevOps. Manage repos, pipelines, work items, and pull requests.
Enable AI agents to fix build failures from CircleCI. Debug CI pipelines and analyze test results.
Official MCP server for dbt (data build tool). Manage models, run transformations, query semantic layer.
Access Harness platform data including pipelines, repositories, and deployments.
If Buildkite doesn't fit your stack, these DevOps MCP servers solve similar problems.
The Buildkite MCP server is an DevOps Model Context Protocol server that lets Claude Code, Cursor, Windsurf, VS Code with Copilot, and other MCP-compatible AI agents manage Buildkite pipelines and builds. It exposes Buildkite's capabilities as tools the AI can call directly from your editor or CLI.
The fastest way is the MCPizy CLI: run `mcpizy install buildkite` and MCPizy will add the server to your `.claude.json` automatically. You can also install it manually by adding an entry under `mcpServers` in `.claude.json` with the command `npx -y @buildkite/mcp-server` and restarting Claude Code.
Yes. The Buildkite MCP server is free and open source (see the GitHub repository linked on this page). You may still need a Buildkite account or API key to connect the server to the underlying service, but the MCP layer itself has no MCPizy subscription cost.
Yes. Any MCP-compatible client works — including Claude Code, Claude Desktop, Cursor (via `.cursor/mcp.json`), Windsurf, VS Code with Copilot Chat, and custom agents built on the MCP SDK. The same install command targets all of them; only the config file path differs.
Once installed, your AI agent can manage Buildkite pipelines and builds directly inside your conversation. Typical use cases include asking Claude Code or Cursor to run Buildkite operations, inspect results, chain Buildkite with other MCP servers (see our Workflow Recipes), and automate repetitive devops tasks without leaving your editor.