Ext Ops Panel
Open dashboard
Comparison

DevHub CMS vs Sellbase

DevHub CMS is an MCP server published by devhub. Marketplaces we read that list it: 1 (Docker MCP Catalog). Sellbase is an MCP server published by jlgavel011. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceDevHub CMSSellbase
Docker MCP Catalog Listed
Version: sha256:d09cf1f01b09
Forks (GitHub): 12
Pulls (Docker Hub): 18 112
Stars (Docker Hub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.3
Downloads/month (npm): 745
Downloads/week (npm): 58
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

DevHub CMS vs Sellbase
FactDevHub CMSSellbase
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)2 (worse)
Pulls (Docker Hub) (differs)18 112No figure on Docker Hub
Forks (GitHub) (differs)12 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/devhub-cms)On your machine (sellbase)
Transportstdiostdio
Tools it declares (differs)10Not published
Environment variables it asks for (differs)3, secrets among them: 23, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/devhub/devhub-cms-mcpgithub.com/jlgavel011/sellbase
Changes in the last 7 days (differs)02
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

DevHub CMS

In its own words, on Docker MCP Catalog:

DevHub CMS LLM integration through the Model Context Protocol.

Sellbase

In its own words, on Official MCP Registry:

Open source commerce in your own Supabase: catalog, checkout, orders and bookings, run by your AI.

How to run each

DevHub CMS As a local MCP server: Docker image

Claude Code
claude mcp add --env "DEVHUB_API_KEY=<YOUR_DEVHUB_API_KEY>" --env "DEVHUB_API_SECRET=<YOUR_DEVHUB_API_SECRET>" --transport stdio devhub-cms -- docker run -i --rm -e DEVHUB_API_KEY -e DEVHUB_API_SECRET mcp/devhub-cms

Requires: DEVHUB_API_KEY (secret), DEVHUB_API_SECRET (secret)

Sellbase As a local MCP server: npm package

Claude Code
claude mcp add --env "SELLBASE_API_TOKEN=<YOUR_SELLBASE_API_TOKEN>" --env "SELLBASE_URL=<YOUR_SELLBASE_URL>" --transport stdio sellbase -- npx -y sellbase mcp

Requires: SELLBASE_API_TOKEN (secret), SELLBASE_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 Sellbase publish no list of tools, so we do not compare tools.

Settings each asks for

Only DevHub CMS asks for

  • DEVHUB_API_KEY (secret)
  • DEVHUB_API_SECRET (secret)
  • DEVHUB_BASE_URL

Only Sellbase asks for

  • SELLBASE_API_TOKEN (secret)
  • SELLBASE_URL
  • SUPABASE_ANON_KEY

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

What it can do: DevHub CMS · What it can do: Sellbase · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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