Buildkite MCP Server 4c2bdfb4

MCP开发工具

提供方 wolfeidau

开发工具 stdio · 本地进程 无需鉴权 社区 / 第三方

This is an mcp server for buildkite.

一句话选型结论

按资料字段整理

Buildkite MCP Server 4c2bdfb4 属于开发工具类 MCP 服务器,stdio · 本地进程,无需鉴权,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

developer-toolsbuildkitemcp-server

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Buildkite MCP Server 4c2bdfb4当前 未标注 stdio · 本地进程 本地部署 无 2026-05-18
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方wolfeidau上游标注的维护方 wolfeidau
分类开发工具本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-18上游最后核验时间

详细介绍

10.4 KB
来自项目仓库与上游目录的原文,未做删改

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.```bash
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.

Follow the manual GitHub Actions setup.
Keep branch-wide `skip_queued_branch_builds` and `cancel_running_branch_builds`
false to avoid skipping or cancelling sibling workflow builds. Use
`create_webhook: false`: provider settings do not provision a dedicated GitHub
Actions trigger or its webhook, and the existing webhook tools create
traditional repository webhooks. Server-side feature availability and token
permissions still apply; accepting settings does not prove workflow execution.

On create, supply nonblank `configuration` **or** an approved
`pipeline_template_uuid`, not both. On update, omit `pipeline_template_uuid`
to retain the assignment, supply a UUID to assign a template without
`configuration`, or send `null` to remove it. Removal can include replacement
`configuration`; the API enforces configuration requirements and organization
template policy. Full pipeline responses retain assigned UUIDs; go-buildkite
omits the field when the response assignment is null or absent.

Use `get_pipeline_github_webhook_processing`,
`enable_pipeline_github_webhook_processing`, and
`disable_pipeline_github_webhook_processing` to inspect or change traditional
GitHub webhook processing. These use GET/PUT/DELETE `github-webhooks`, not the
POST `webhook` creation endpoint. They do not delete repository webhooks or
change dedicated GitHub Actions triggers. Responses preserve `enabled` and
nullable `disabled_at` and `disabled_by` metadata; `disabled_by` is a user name.
All three require Full Access, a GitHub or GitHub Enterprise pipeline, and
organization enrollment in expanded webhook triggers. GET requires
`read_pipelines`; enable/disable require `write_pipelines` and are excluded in
read-only mode. A 404 can mean the controls are unavailable, not that the
pipeline is missing. API errors are returned without treating failure as a
disabled state.

These contracts are covered with local synthetic HTTP fixtures. Hosted
availability, permissions, persistence, and workflow execution require separate
verification; local success is not proof of deployed support. Dedicated GitHub
Actions trigger management is not included.

---

## Comparing builds

The read-only `compare_builds` tool in the `investigations` toolset answers questions such as “What changed since this build last worked on main?” Supply `org_slug`, `pipeline_slug`, and the target `build_number`. It selects the most recently created earlier build that is currently passed on the same pipeline and exact branch. It does not require that the baseline had already passed when the target started. Supply `baseline_build_number` to compare against a specific build in that pipeline instead, including a failed build or one on another branch.

The response identifies the baseline and selection rule, counts outcomes across all jobs, and returns up to 100 job comparisons, prioritizing newly failing, recovered, and still-failing steps. Matching uses step keys, job type, matrix values, and parallel index/total. When both jobs lack keys, it falls back to the exact nonblank name plus type, group key, matrix values, and parallel index/total, only when that combination is unique in each build. Matched pairs expose `match_method: "step_key"` or `"name_fallback"`; fallback matches carry a warning that they are heuristic. Unnamed unkeyed jobs and duplicate identities remain unmatched. Explicit keys never fall back to names, even when a key was added, removed, or changed between builds. Added/removed means a job identity is present in only one build, so renaming unkeyed jobs or changing matrix values or parallelism can also produce added/removed entries. Retried attempts are excluded; final-attempt states and retry counts remain visible.

Execution times and deltas cover final attempts only. Scheduling time is `scheduled_at` to `started_at`, not dependency or manual waiting. These are not build wall-clock comparisons or total retry costs. Missing or inconsistent timestamps omit the corresponding timing. Unfinished builds are explicitly identified as changing snapshots.

Any change in `soft_failed` is reported as `state_changed`: transitions between soft and hard failures, even when both jobs have state `failed`, and between passed and soft-failed jobs, which are never reported as `newly_failing` or `recovered` because a soft failure does not block the build. A passed baseline build can contain soft-failed jobs.

By default, up to three newly blocking failures include their last 20 log entries: `newly_failing` jobs first, then `state_changed` jobs that are now hard failures, such as a job that soft-failed in the baseline. Logs are bounded to 8 KiB of log content each. Set `include_logs: false` to omit logs. Log errors do not discard the comparison, except HTTP 401 authentication errors, which propagate through the server's reauthentication path. The tool requires `read_builds` and `read_build_logs` scopes. Use `get_build_failure_summary` or `tail_logs` to investigate further; a shared failing step does not establish a shared root cause or make a retry safe.

Baseline discovery searches at most 500 candidates. If none is found, the response says no comparison was performed and asks for an explicit baseline. Job inventories are limited to 1,000 jobs per build; larger inventories return an error instead of misleading partial added/removed results. Output omissions are reported separately from the complete outcome counts.

---

## Inspecting Test Engine workflows

The read-only `list_test_workflows` and `get_test_workflow` tools in the `tests`
toolset expose a suite's configured monitors, filters, alarm/recovery actions,
and links. Both require `read_suites` and suite access. Supply `org_slug` and
`test_suite_slug` (a slug or UUID) to list workflows:```json
{"org_slug": "acme", "test_suite_slug": "backend"}

To inspect one, call get_test_workflow with the same organization and suite
and an item's id as workflow_id.

Use the configured labels with list_tests to find marked tests; labels alone
do not rank flakiness. Workflows describe configuration, not proof an action
ran or event history. Both tools always replace webhook endpoints with
[REDACTED], regardless of the caller's API permissions.


Library Usage

The exported Go API of this module should be considered unstable, and subject to breaking changes as we evolve this project.


Security

To ensure the MCP server is run in a secure environment, we recommend running it in a container.

This image is built from cgr.dev/chainguard/static and runs as an unprivileged user.

Passing identity headers through HTTP mode

Self-hosted HTTP deployments can forward selected headers from each inbound MCP request to the Buildkite API:```bash
BUILDKITE_API_TOKEN=bkua_xxx \
buildkite-mcp-server http \
--passthrough-http-header X-User-Identity


Repeat `--passthrough-http-header` to allow more than one header, or set a comma-separated `BUILDKITE_PASSTHROUGH_HTTP_HEADERS` value. Only explicitly allowed headers are forwarded, and only to the origin configured by `BUILDKITE_BASE_URL`. They are removed from requests redirected elsewhere.

To authenticate each MCP request with its own Buildkite API token, allow `Authorization` and omit the process-wide token:```bash
BUILDKITE_PASSTHROUGH_HTTP_HEADERS=Authorization \
  buildkite-mcp-server http

In this mode every /mcp request must contain exactly one non-empty Authorization header. Missing credentials return HTTP 401; the server never falls back to a shared API token. The reverse proxy in front of the MCP server is responsible for authenticating callers and setting or validating any forwarded identity headers.

Header passthrough is not available in stdio mode. Before serving job logs, the server verifies that the current caller can access the job log. This check is performed for every log-tool request, including when the log data is already cached.


Contributing

Development guidelines are in DEVELOPMENT.md.


License

MIT © Buildkite

SPDX-License-Identifier: MIT

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Buildkite MCP Server 4c2bdfb4 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Buildkite MCP Server 4c2bdfb4 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Buildkite MCP Server 4c2bdfb4 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Buildkite MCP Server 4c2bdfb4 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Buildkite MCP Server 4c2bdfb4 能提供哪些能力?

资料显示能力标签包括 开发工具、日志管理、API集成。具体工具清单以官方文档为准。

Buildkite MCP Server 4c2bdfb4 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Buildkite MCP Server 4c2bdfb4 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-18。