What's new in the Buildkite MCP server (buildkite.com)

Buildkite has released a major update to its MCP (Model Control Plane) server: a new fully managed remote server (OAuth-secured), far more efficient log fetching/parsing, and specialized tooling for monitoring running builds. The remote server requires no local install—just point your AI tool at https://mcp.buildkite.com/mcp (or the read-only /mcp/readonly endpoint) and use your tool’s browser OAuth flow; tokens are short-lived (12 hours) and auto-refreshed for up to seven days. These changes are aimed squarely at making AI agents practical in CI/CD workflows by reducing maintenance, security risk from long-lived keys, and token/context waste that previously made agent-driven debugging ineffective. Technically, Buildkite now converts fetched build logs into Apache Parquet and caches them, returning compact, structured JSON snippets rather than multi-megabyte raw logs—this shrinks token usage and yields faster, more accurate agent responses; remote caches are shared on the Buildkite platform, while local servers can use S3 for shared caches. They also added wait_for_build, a polling-and-streaming tool that minimizes API churn while waiting on in-progress builds, plus tools like create_pipeline to bootstrap pipelines. Docs are now Markdown-friendly and preloaded into Context7 for LLMs. Altogether, these updates lower friction for agent-enabled CI, improve observability, and make agent-assisted build triage and automation far more practical.