Buildkite buildkite

Inspect Buildkite pipelines, builds, jobs, logs, annotations and test results, and trigger builds, with an API token you supply as a named secret.

Homepage: https://github.com/buildkite/buildkite-mcp-server
License: MIT
Runtime: native, transport stdio
Categories: ci

Versions

Version	Published	Runtime	Blobs
1.22.0	2026-10-06T14:04:59Z	`native`	linux/amd64 `3a92ef529da59fe1c7719fac83fbb286b57a9b5ef79daf22b621b34fd720f2ad` 14.5 MiB curl -fsSLO https://library.pellum.ai/blobs/sha256/3a92ef529da59fe1c7719fac83fbb286b57a9b5ef79daf22b621b34fd720f2ad

Parameters

Name	Type	Environment	Required	Secret	Description
`api_token`	string	`BUILDKITE_API_TOKEN`	yes	yes	Buildkite API access token with the scopes you want exposed.

Credentials

The server verifies no caller token. The executor's sandbox and listener are the controls on who may call it.

Egress

Destination	Port	Reason
`api.buildkite.com`	default web ports	the Buildkite REST API every tool calls

A host of the form ${param.host} is the host of a URL the operator supplies, resolved by the gateway at claim time. The library never knows it.

Resource defaults

memory.max 256Mi, pids.max 128, cpu.max 100000 100000.

Verify a download

Against the library key, which is what a gateway checks:

curl -fsSLO https://library.pellum.ai/blobs/sha256/3a92ef529da59fe1c7719fac83fbb286b57a9b5ef79daf22b621b34fd720f2ad
curl -fsSLO https://library.pellum.ai/blobs/sha256/3a92ef529da59fe1c7719fac83fbb286b57a9b5ef79daf22b621b34fd720f2ad.sig
curl -fsSLO https://library.pellum.ai/keys/library-v1.pub
echo "3a92ef529da59fe1c7719fac83fbb286b57a9b5ef79daf22b621b34fd720f2ad  3a92ef529da59fe1c7719fac83fbb286b57a9b5ef79daf22b621b34fd720f2ad" | sha256sum -c -
cosign verify-blob --insecure-ignore-tlog --key library-v1.pub --signature 3a92ef529da59fe1c7719fac83fbb286b57a9b5ef79daf22b621b34fd720f2ad.sig 3a92ef529da59fe1c7719fac83fbb286b57a9b5ef79daf22b621b34fd720f2ad