Ext Ops Panel
Open dashboard
Comparison

Spinnaker vs io.github.kubeshop/testkube-mcp

Spinnaker is an MCP server published by GeiserX. Marketplaces we read that list it: 1 (Official MCP Registry). 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-30. 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

Where each is published
MarketplaceSpinnakerio.github.kubeshop/testkube-mcp
Official MCP Registry Listed
Version: 0.4.1
Downloads/month (npm): 913
Downloads/week (npm): 64
Forks (GitHub): 1
Stars (GitHub): 5
Not marked · First seen
Listed
Version: 2.15.0
Forks (GitHub): 180
Stars (GitHub): 1 677
Not marked · First seen
Docker MCP Catalog Not listed Listed
Version: sha256:43aa88f2d416
Forks (GitHub): 180
Pulls (Docker Hub): 34 120
Stars (Docker Hub): 0
Stars (GitHub): 1 677
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

Spinnaker vs io.github.kubeshop/testkube-mcp
FactSpinnakerio.github.kubeshop/testkube-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)5 (worse)1 677 (better)
Pulls (Docker Hub) (differs)No figure on Docker Hub34 120
Forks (GitHub) (differs)1 (worse)180 (better)
Last release (differs)2026-10-28 (worse)2026-10-29 (better)
Where it runs (differs)On your machine (spinnaker-mcp)Remote server or your machine
Transport (differs)stdioStreamable HTTP, stdio
Tools it declares (differs)Not published28
Environment variables it asks for (differs)10, secrets among them: 37, secrets among them: 2
Licence (differs)Not statedNOASSERTION
Repository (differs)github.com/geiserx/spinnaker-mcpgithub.com/kubeshop/testkube
Changes in the last 7 days (differs)43
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 26 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

Spinnaker

In its own words, on Official MCP Registry:

MCP server exposing Spinnaker CD platform via Gate API for pipeline and deployment management

io.github.kubeshop/testkube-mcp

In its own words, on Official MCP Registry:

MCP server for Testkube - Manage test workflows, executions, and artifacts via AI assistants

How to run each

Spinnaker As a local MCP server: npm package

Claude Code
claude mcp add --env "GATE_COOKIE=<YOUR_GATE_COOKIE>" --env "GATE_PASS=<YOUR_GATE_PASS>" --env "GATE_TOKEN=<YOUR_GATE_TOKEN>" --env "GATE_URL=<YOUR_GATE_URL>" --transport stdio spinnaker-mcp -- npx -y spinnaker-mcp

Requires: GATE_COOKIE (secret), GATE_PASS (secret), GATE_TOKEN (secret), GATE_URL

io.github.kubeshop/testkube-mcp As a local MCP server: Docker image

Claude Code
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/testkube

Requires: 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 Spinnaker publish no list of tools, so we do not compare tools.

Settings each asks for

Only Spinnaker asks for

  • GATE_CERT_FILE
  • GATE_COOKIE (secret)
  • GATE_COOKIE_FILE
  • GATE_INSECURE
  • GATE_KEY_FILE
  • GATE_PASS (secret)
  • GATE_TOKEN (secret)
  • GATE_URL
  • GATE_USER
  • TOOLSETS

Only io.github.kubeshop/testkube-mcp asks for

  • TK_ACCESS_TOKEN (secret)
  • TK_CONTROL_PLANE_URL
  • TK_DASHBOARD_URL
  • TK_DEBUG
  • TK_ENV_ID (secret)
  • TK_MCP_SHTTP_AUTH_TOKEN (secret)
  • TK_ORG_ID (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Spinnaker · What it can do: io.github.kubeshop/testkube-mcp · 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.

Where the data comes from: how the catalog is built