prepare-delivery vs io.github.kubeshop/testkube-mcp
prepare-delivery is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.kubeshop/testkube-mcp is an MCP server published by kubeshop. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-23. 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 |  prepare-delivery |  io.github.kubeshop/testkube-mcp |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.14.2 Forks (GitHub): 180 Stars (GitHub): 1 674 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:43aa88f2d416 Forks (GitHub): 180 Pulls (Docker Hub): 33 800 Stars (Docker Hub): 0 Stars (GitHub): 1 674 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 | prepare-delivery | io.github.kubeshop/testkube-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (worse) | 1 674 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 33 800 |
| Forks (GitHub) (differs) | 0 (worse) | 180 (better) |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 28 |
| Environment variables it asks for (differs) | Not published | 9, secrets among them: 1 |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | MIT | NOASSERTION |
| Repository (differs) | github.com/agent-sh/prepare-delivery | github.com/kubeshop/testkube |
| 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 33 h ago, requires a key |
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
prepare-delivery
Pre-ship quality gates without the ship. Runs the full pre-merge pipeline — deslop (clean AI debris), simplify (de-bloat), agnix (lint agent configs), enhance (audit prompts/skills/hooks/plugins/docs), multi-agent review (audit-project), test-coverage check, delivery validation, sync-docs — and produces a unified pass/fail report. Doesn't push, doesn't create PRs, doesn't merge — just gates. Designed for the workflow where you want all the quality enforcement but the actual ship step happens later (or via a separate /ship invocation, or by hand).
io.github.kubeshop/testkube-mcp
MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants
How to run each
prepare-delivery As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install prepare-delivery@claude-communityio.github.kubeshop/testkube-mcp As a local MCP server: Docker image
claude mcp add --env "TK_ACCESS_TOKEN=<YOUR_TK_ACCESS_TOKEN>" --env "TK_ENV_ID=<YOUR_TK_ENV_ID>" --env "TK_ORG_ID=<YOUR_TK_ORG_ID>" --transport stdio testkube -- docker run -i --rm -e TK_ACCESS_TOKEN -e TK_ENV_ID -e TK_ORG_ID mcp/testkubeRequires: TK_ACCESS_TOKEN (secret), TK_ENV_ID (secret), TK_ORG_ID (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.kubeshop/testkube-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of prepare-delivery publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of prepare-delivery publish no settings it asks for, so we do not compare settings.
What it can do: prepare-delivery · What it can do: io.github.kubeshop/testkube-mcp · 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.