Ext Ops Panel
Open dashboard
Comparison

StackGen vs Bult

StackGen is an MCP server published by stackgenhq. Marketplaces we read that list it: 1 (Docker MCP Catalog). Bult is an MCP server published by bultcloud. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceStackGenBult
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.0.1
Downloads/month (npm): 171
Downloads/week (npm): 20
Forks (GitHub): 0
Stars (GitHub): 2
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 Bult
FactStackGenBult
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)2 (better)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (ghcr.io/stackgenhq/stackgen)On your machine (@bultcloud/mcp-server)
Transportstdiostdio
Tools it declares (differs)4Not published
Environment variables it asks for2, secrets among them: 12, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/stackgenhq/homebrew-stackgengithub.com/bultcloud/mcp-server
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.

Bult

In its own words, on Official MCP Registry:

Deploy and manage Bult apps from AI coding agents.

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)

Bult As a local MCP server: npm package

Claude Code
claude mcp add --env "BULT_API_TOKEN=<YOUR_BULT_API_TOKEN>" --env "BULT_API_URL=<YOUR_BULT_API_URL>" --transport stdio bult -- npx -y @bultcloud/mcp-server

Requires: BULT_API_TOKEN (secret), BULT_API_URL

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of Bult 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 Bult asks for

  • BULT_API_TOKEN (secret)
  • BULT_API_URL

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

What it can do: StackGen · What it can do: Bult · 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