supertool vs io.github.kubeshop/testkube-mcp
supertool is a plugin bundle for AI coding tools published by Digital-Process-Tools. 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-18. 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 |  supertool |  io.github.kubeshop/testkube-mcp |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.27.0 Forks (GitHub): 3 Stars (GitHub): 26 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.14.0 Forks (GitHub): 179 Stars (GitHub): 1 669 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:43aa88f2d416 Forks (GitHub): 179 Pulls (Docker Hub): 33 682 Stars (Docker Hub): 0 Stars (GitHub): 1 669 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 | supertool | io.github.kubeshop/testkube-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 26 (worse) | 1 669 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 33 682 |
| Forks (GitHub) (differs) | 3 (worse) | 179 (better) |
| Last release | Not published | Not published |
| 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 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Community License | NOASSERTION |
| Repository (differs) | github.com/digital-process-tools/claude-supertool | github.com/kubeshop/testkube |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days 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
supertool
Batch multiple file operations (read, grep, glob, ls, tail, head) into a single Bash round-trip. Instead of N separate Read/Grep/Glob tool calls — each re-paying the cached context prefix — one ./supertool call handles them all. Includes auto-promote (concrete glob becomes read, single-file grep includes full file), enforcement mode that blocks redundant built-in tools, and per-call logging with caller tracking. Python 3.6+, stdlib-only, 80 tests.
io.github.kubeshop/testkube-mcp
MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants
How to run each
supertool As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install supertool@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 supertool publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of supertool publish no settings it asks for, so we do not compare settings.
What it can do: supertool · 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.