io.github.buildkite/buildkite-mcp-server
MCP server · buildkite
- On your machine
io.github.buildkite/buildkite-mcp-server is an MCP server published by buildkite. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). We first saw it on 2026-10-11 and have recorded no change since. As of our marketplace pass on 2026-10-11.
MCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors.
- Marketplaces
- 2
- Where it runs
- On your machine
ghcr.io/buildkite/buildkite-mcp-server:0.7.0 - Largest published figure
- 13 189 Pulls (Docker Hub) · Docker MCP Catalog
- First seen
- 2026-10-11
- Last change
- None recorded
- Verified mark
- Not marked
Where it is published
| Marketplace | Status | Version | Figures | Verified | First seen |
|---|---|---|---|---|---|
| Official MCP Registry (Open the registry record) | Listed | 0.7.0 | Forks (GitHub): 39 Stars (GitHub): 55 |
Not marked | |
| Docker MCP Catalog (Open on Docker Hub) | Listed | sha256:00e13d1742a5 | Pulls (Docker Hub): 13 189 Stars (Docker Hub): 0 |
Not marked |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
What it can do
Runs on your machine, in a container started from this image: ghcr.io/buildkite/buildkite-mcp-server:0.7.0
- Tools it declares
- 24
- Environment variables it asks for
- 1 secrets among them: 1
What changed
Nothing has moved on this plugin since we started watching it.
The publisher
buildkite · Repository: github.com/buildkite/buildkite-mcp-server
Possibly the same plugin
Listings that share a signal with this one but not enough for us to treat them as the same product.
Similar plugins
We have not computed this plugin's meaning vector yet. Similar plugins appear after the next update.
Is this your plugin?
Prove you maintain it with a file in its repository, a file on your domain or a DNS record. You get alerts when a marketplace lists it, drops it, changes its verified mark or what it asks for, and can put its remote endpoint on monitoring as a web service.
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.