atelier-pipeline vs io.github.buildkite/buildkite-mcp-server
atelier-pipeline is a plugin bundle for AI coding tools published by robertsfeir. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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). As of our marketplace pass on 2026-11-08. 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 |  atelier-pipeline |  io.github.buildkite/buildkite-mcp-server |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 5.2.0 Forks (GitHub): 8 Stars (GitHub): 25 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.0 Forks (GitHub): 40 Stars (GitHub): 56 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:00e13d1742a5 Forks (GitHub): 40 Pulls (Docker Hub): 13 643 Stars (Docker Hub): 0 Stars (GitHub): 56 Not marked · First seen |
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 | atelier-pipeline | io.github.buildkite/buildkite-mcp-server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 25 (worse) | 56 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 13 643 |
| Forks (GitHub) (differs) | 8 (worse) | 40 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (ghcr.io/buildkite/buildkite-mcp-server:0.7.0) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 24 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/robertsfeir/atelier-pipeline | github.com/buildkite/buildkite-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
atelier-pipeline
Atelier Pipeline has two core systems: Multi-Agent Orchestration. Eleven specialized agent personas with clear responsibilities, strict boundaries, and independent quality verification. Eva orchestrates, Robert handles product, Sable designs UX, Sarah architects, Colby builds, Poirot blind-reviews every wave, Agatha documents, Ellis commits, Distillator compresses cross-phase artifacts, Sherlock investigates user-reported bugs, and Sentinel audits security (opt-in). Custom agents can be added via agent discovery. Specs get written, designs get validated, every change passes Eva's mechanical test gate plus Poirot blind review, and nothing ships without review. Works with Claude Code and Cursor. Atelier Brain. A persistent memory layer backed by PostgreSQL and vector embeddings that gives your agents institutional memory across sessions. Without it, every time you close a terminal you lose the architectural decisions that shaped your implementation, the user corrections that steered scope, the rejected alternat
io.github.buildkite/buildkite-mcp-server
MCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors.
How to run each
atelier-pipeline As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install atelier-pipeline@claude-communityio.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.0Requires: BUILDKITE_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of atelier-pipeline publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of atelier-pipeline publish no settings it asks for, so we do not compare settings.
What it can do: atelier-pipeline · What it can do: io.github.buildkite/buildkite-mcp-server · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.