模型上下文协议（MCP）服务器，向AI工具和编辑器展示Buildkite数据（流水线、构建、作业、测试）。

完整文档可在 buildkite.com/docs/apis/mcp-server 获取。

---

重试有限权限的构建

retries 工具集支持调查失败和重试作业，无需 更广泛的构建-写入访问。它包括 list_builds、get_build， wait_for_build， list_jobs， get_job、search_logs、tail_logs、read_logs， retry_job，和retry_failed_jobs。它需要read_builds， read_build_logs和retry_builds示波器，而非write_builds。

retry_failed_jobs 只重试基础设施故障;使用其 dry_run 允许检查拟议重试而非执行它们。retry_job 重试特定作业。两者都是变异工具，且被排除在 --read-only。该工具集不暴露创建、重建、取消或解除阻挡 操作。现有的重试工具仍可在builds中使用;选择 builds 或 all 仍需 write_builds 来处理其他突变。

Buildkite API 必须启用 RetryBuildsScope 功能以实现令牌

buildkite-mcp-server

Model Context Protocol (MCP) server exposing Buildkite data (pipelines, builds, jobs, tests) to AI tooling and editors.

Full documentation is available at buildkite.com/docs/apis/mcp-server.

---

Retrying builds with limited permissions

The retries toolset supports investigating failures and retrying jobs without broader build-write access. It includes list_builds, get_build, wait_for_build, list_jobs, get_job, search_logs, tail_logs, read_logs, retry_job, and retry_failed_jobs. It requires read_builds, read_build_logs, and retry_builds scopes, not write_builds.

buildkite-mcp-server stdio --enabled-toolsets retries

retry_failed_jobs retries only infrastructure failures; use its dry_run option to inspect the proposed retries without executing them. retry_job retries a specific job. Both are mutating tools and are excluded by --read-only. The toolset does not expose create, rebuild, cancel, or unblock operations. Existing retry tools remain available in builds; selecting builds or all still requires write_builds for the other mutations.

The Buildkite API must have the RetryBuildsScope feature enabled for the token owner to accept retry_builds; existing write_builds tokens remain accepted. Hosted MCP OAuth can select this toolset using /mcp/x/retries once the hosted server adopts a release containing it. Selecting toolsets through request headers does not change an existing token’s OAuth scopes.

For library consumers, WithDisabledToolsets and the HTTP factory’s disabled toolsets exclude all members of those toolsets, even through overlapping groups. For example, disabling logs also removes log tools from retries; disabling retries removes its inspection and retry tools from other groups.

---

Configuring GitHub Actions pipelines

create_pipeline and update_pipeline accept GitHub provider_settings and branch_configuration. Omit provider keys to use API defaults on create or leave them unchanged on update. Explicit false is preserved. Set filter_condition or pull_request_branch_filter_configuration to null to clear them; an empty string is sent as an empty string. Set branch_configuration: null on update to clear an existing branch filter. On create, an omitted, null or empty branch filter uses the API’s null default. Full get_pipeline and list_pipelines responses preserve the supported GitHub settings. go-buildkite response strings do not distinguish null from empty, so do not reconstruct partial updates from readback.