Ext Ops Panel
Open dashboard
Comparison

StackGen vs io.github.kastelldev/kastell

StackGen is an MCP server published by stackgenhq. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.kastelldev/kastell is an MCP server published by kastelldev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceStackGenio.github.kastelldev/kastell
Docker MCP Catalog Listed
Version: sha256:e0bab64f662a
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.14.0
Downloads/month (npm): 790
Downloads/week (npm): 108
Forks (GitHub): 2
Stars (GitHub): 60
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

StackGen vs io.github.kastelldev/kastell
FactStackGenio.github.kastelldev/kastell
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)60 (better)
Forks (GitHub) (differs)1 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ghcr.io/stackgenhq/stackgen)On your machine (kastell)
Transportstdiostdio
Tools it declares (differs)4Not published
Environment variables it asks for (differs)2, secrets among them: 14, secrets among them: 4
LicenceNot statedNot stated
Repository (differs)github.com/stackgenhq/homebrew-stackgengithub.com/kastelldev/kastell
Changes in the last 7 days00
First seen2026-10-112026-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

StackGen

In its own words, on Docker MCP Catalog:

AI-powered DevOps assistant for managing cloud infrastructure and applications.

io.github.kastelldev/kastell

In its own words, on Official MCP Registry:

Server security audit (413 checks), hardening, and fleet management across 4 cloud providers.

How to run each

StackGen As a local MCP server: Docker image

Claude Code
claude mcp add --env "STACKGEN_TOKEN=<YOUR_STACKGEN_TOKEN>" --transport stdio stackgen -- docker run -i --rm -e STACKGEN_TOKEN ghcr.io/stackgenhq/stackgen

Requires: STACKGEN_TOKEN (secret)

io.github.kastelldev/kastell As a local MCP server: npm package

Claude Code
claude mcp add --env "DIGITALOCEAN_TOKEN=<YOUR_DIGITALOCEAN_TOKEN>" --env "HETZNER_TOKEN=<YOUR_HETZNER_TOKEN>" --env "LINODE_TOKEN=<YOUR_LINODE_TOKEN>" --env "VULTR_TOKEN=<YOUR_VULTR_TOKEN>" --transport stdio kastell -- npx -y kastell

Requires: DIGITALOCEAN_TOKEN (secret), HETZNER_TOKEN (secret), LINODE_TOKEN (secret), VULTR_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 io.github.kastelldev/kastell publish no list of tools, so we do not compare tools.

Settings each asks for

Only StackGen asks for

  • STACKGEN_TOKEN (secret)
  • STACKGEN_URL

Only io.github.kastelldev/kastell asks for

  • DIGITALOCEAN_TOKEN (secret)
  • HETZNER_TOKEN (secret)
  • LINODE_TOKEN (secret)
  • VULTR_TOKEN (secret)

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

What it can do: StackGen · What it can do: io.github.kastelldev/kastell · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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