Model Context Protocol (MCP) 서버는 Buildkite 데이터 (파이프 라인, 빌드, 작업, 테스트)를 AI 툴링 및 편집기에 배포합니다.

전체 문서는 buildkite.com/docs/apis/mcp-server에서 사용할 수 있습니다.

---

Retrying는 제한된 권한으로 빌드합니다.

retries 툴렛은 투자 실패와 재난 작업을 지원 더 넓은 build-write 접근. 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 retries 만의 인프라 실패; 사용 dry_run] 그들을 실행하지 않고 제안 된 retries를 검사하는 옵션. retry_job] 특정 작업을 retries. 둘 다 mutating 공구는에 의해 제외됩니다 --read-only. 도구 모음은 생성, 재건, 취소, 또는 차단하지 않습니다 작업. 기존 리트리 도구는 builds]에서 사용할 수 있습니다. 선택 builds 또는 all]는 여전히 다른 mutations에 대한 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.