io.github.buildkite/buildkite-mcp-server vs Michigan Code
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). Michigan Code is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.7.0 Forks (GitHub): 40 Stars (GitHub): 56 Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:00e13d1742a5 Forks (GitHub): 40 Pulls (Docker Hub): 13 626 Stars (Docker Hub): 0 Stars (GitHub): 56 Not marked · First seen |
Not listed |
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.
The facts side by side
| Fact | io.github.buildkite/buildkite-mcp-server | Michigan Code |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 56 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 13 626 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 40 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | On your machine (ghcr.io/buildkite/buildkite-mcp-server:0.7.0) | Remote server (gateway.pipeworx.io/michigan-code/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 24 | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/buildkite/buildkite-mcp-server | github.com/pipeworx-io/mcp-michigan-code |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 8 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.buildkite/buildkite-mcp-server
MCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors.
Michigan Code
Michigan Compiled Laws (statutes) and, since fleet #3957, the Michigan Administrative Code (agency…
How to run each
io.github.buildkite/buildkite-mcp-server As a local MCP server: Docker image
claude mcp add --env "BUILDKITE_API_TOKEN=<YOUR_BUILDKITE_API_TOKEN>" --transport stdio buildkite-mcp-server -- docker run -i --rm -e BUILDKITE_API_TOKEN run BUILDKITE_API_TOKEN ghcr.io/buildkite/buildkite-mcp-server:0.7.0 ghcr.io/buildkite/buildkite-mcp-server:0.7.0
Requires: BUILDKITE_API_TOKEN (secret)
Michigan Code As a remote MCP server
claude mcp add --transport http michigan-code https://gateway.pipeworx.io/michigan-code/mcp
Requires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Michigan Code has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Michigan Code publish no list of tools, so we do not compare tools.
Settings each asks for
Only io.github.buildkite/buildkite-mcp-server asks for
BUILDKITE_API_TOKEN (secret)
Only Michigan Code asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.buildkite/buildkite-mcp-server · What it can do: Michigan Code · Compare two other plugins
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.