Can AI agents automate Buildkite?

Buildkite is automatable today through its REST API at https://api.buildkite.com/v2. This record is Buildkite Pipelines and Test Engine. It is not CircleCI, Jenkins, or GitHub Actions. REST v2 is JSON over HTTPS. Callers send Authorization: Bearer with a scoped API access token. A preview public-key credential signs short-lived RS256 JWTs as Bearer tokens after Buildkite enables it for the organization. GraphQL is at https://graphql.buildkite.com/v1 with the same Bearer header and an Enable GraphQL API Access permission. Documented REST resources include organizations, pipelines, builds, jobs, agents, clusters, artifacts, annotations, teams, and Test Engine analytics. Pipeline webhooks POST JSON for build, job, and agent events and can be verified with X-Buildkite-Token or HMAC X-Buildkite-Signature. The official remote MCP is at https://mcp.buildkite.com/mcp (OAuth), https://mcp.buildkite.com/direct (API-token pass-through), and https://mcp.buildkite.com/mcp/readonly. Tools cover pipelines, builds, jobs, logs, artifacts, annotations, clusters, agents, and Test Engine. Some MCP responses return a subset of REST fields. Remote MCP traffic is rate-limited separately from the organization REST quota. The official local server is github.com/buildkite/buildkite-mcp-server. The official bk CLI installs on Debian/Ubuntu, Red Hat, macOS, and Windows and covers auth, builds, jobs, pipelines, and bk api. Language clients listed on the REST page are contributor libraries, not established as official. iPaaS connector catalogs were not opened. Computer-use viability is unassessed. API and MCP both score 8. API is the best path because MCP returns a subset of REST fields and is a separate rate-limited surface; use /direct when a headless agent already has a token.

Best path today: api · Overall automatability: 8/10