Buildkite MCP Server
Official Buildkite MCP server exposing pipelines, builds, jobs, logs, annotations and Test Engine results, hosted (OAuth or token) or self-run, with read-only routes.
Tags
Description
Buildkite recommends the hosted remote server at https://mcp.buildkite.com/mcp (OAuth, for interactive AI tools); headless agents can use https://mcp.buildkite.com/direct with a Buildkite API token as a bearer token, and https://mcp.buildkite.com/mcp/readonly restricts access to read-only. Remote endpoints update automatically and have their own rate limit. The open-source Go server runs locally over stdio or HTTP with --read-only and --enabled-toolsets; a retries toolset can retry failed jobs without full build-write access, and compare_builds explains what changed since a build last passed.
Agent access
Related
- GitHub MCP Server: GitHub's official MCP server: lets agents read repos and code, manage issues and PRs, analyze code and monitor Actions workflows.
- GitLab MCP Server: GitLab's built-in MCP server for working with projects, issues, merge requests, work items and pipelines from MCP clients; GA in GitLab 19.5.
- Sentry MCP: Sentry's remote MCP server for coding agents, focused on developer debugging workflows over the Sentry API.
Guides & comparisons
- DevOps and observability MCP servers compared (Comparison): Eight official MCP servers for infrastructure and operations work (Kubernetes, Terraform, Buildkite, Azure DevOps, Heroku, Datadog, Grafana and Sentry) compared on what they cover, where they run, how they authenticate and how far their read-only modes actually go.
Sources
Machine-readable
- JSON
- Markdown
- Source file on GitHub (edit via pull request)