モデルコンテキストプロトコル(MCP)サーバーは、Buildkiteデータ(パイプライン、ビルド、ジョブ、テスト)をAIツーリングおよびエディタに公開します。

完全なドキュメントは buildkite.com/docs/apis/mcp-server で利用できます。

お問い合わせ

限られた権限でビルドを再試行する

[retries] ツールセットは、失敗の調査とジョブの再試行をサポート より広い build-write アクセス。 [list_builds, [get_build]], [wait_for_build, [list_jobs], [get_job], [search_logs], [[tail_logs]], [[read_logs]], [[[get_job]]]]], [[[[[[search_logs]]]]], [[[[read_logs]]]], [[[[[[[read_logs]]]]]], [[[[[[[[[[[[[[[[[[[[[[[[[[[[get_job]]]]]]]]]]]]]]]]]]]]]]]]]、[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[ retry_job, [retry_failed_jobs]. [[T11]が必要です。 [read_build_logs, [retry_builds]]] スコープではなく [write_builds 。

[[retry_failed_jobs] インフラ障害のみを回復し、[dry_run を使用する それらを実行せずに提案されたretriesを検査するオプション。 [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.