io.github.buildkite/buildkite-mcp-server vs io.github.lapfelix/xcodemcp
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). io.github.lapfelix/xcodemcp is an MCP server published by lapfelix. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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): 39 Stars (GitHub): 56 Not marked · First seen |
Listed Version: 2.1.4 Downloads/month (npm): 260 Downloads/week (npm): 29 Forks (GitHub): 4 Stars (GitHub): 59 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:00e13d1742a5 Forks (GitHub): 39 Pulls (Docker Hub): 13 466 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 | io.github.lapfelix/xcodemcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 56 (worse) | 59 (better) |
| Pulls (Docker Hub) (differs) | 13 466 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 39 (better) | 4 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (ghcr.io/buildkite/buildkite-mcp-server:0.7.0) | On your machine (xcodemcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 24 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/buildkite/buildkite-mcp-server | github.com/lapfelix/xcodemcp |
| 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
io.github.buildkite/buildkite-mcp-server
MCP server exposing Buildkite API data (pipelines, builds, jobs, tests) to AI tooling and editors.
io.github.lapfelix/xcodemcp
Control Xcode directly via JXA for build, test, debug operations with XCLogParser integration
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)
io.github.lapfelix/xcodemcp As a local MCP server: npm package
claude mcp add --transport stdio xcodemcp -- npx -y xcodemcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.lapfelix/xcodemcp publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.lapfelix/xcodemcp publish no settings it asks for, so we do not compare settings.
What it can do: io.github.buildkite/buildkite-mcp-server · What it can do: io.github.lapfelix/xcodemcp · 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.