Ext Ops Panel
Open dashboard
Comparison

DevHub CMS vs lexsis-storefront-skills

DevHub CMS is an MCP server published by devhub. Marketplaces we read that list it: 1 (Docker MCP Catalog). lexsis-storefront-skills is a plugin bundle for AI coding tools published by Aetheria Labs. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-17. 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 CMSlexsis-storefront-skills
Docker MCP Catalog Listed
Version: sha256:d09cf1f01b09
Forks (GitHub): 12
Pulls (Docker Hub): 18 066
Stars (Docker Hub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed
Community marketplace aetheria-labs1/storefront-skills Not listed Listed
Version: 9.6.0
Forks (GitHub): 0
Stars (GitHub): 8
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 lexsis-storefront-skills
FactDevHub CMSlexsis-storefront-skills
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)8 (worse)
Pulls (Docker Hub) (differs)18 066No figure on Docker Hub
Forks (GitHub) (differs)12 (better)0 (worse)
Last release (differs)Not published2026-10-17
Where it runs (differs)On your machine (mcp/devhub-cms)Remote server (mcp.trylexsis.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)10Not published
Environment variables it asks for (differs)3, secrets among them: 2Not published
Parts of the bundle (differs)Not a bundle13
Licence (differs)Not statedMIT
Repository (differs)github.com/devhub/devhub-cms-mcpgithub.com/aetheria-labs1/storefront-skills
Changes in the last 7 days (differs)03
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

lexsis-storefront-skills

In its own words, on Community GitHub marketplaces:

AI storefront generation for Shopify — 10 focused commands, 2 agents, and a full reference corpus.

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)

lexsis-storefront-skills As a Claude Code plugin

Claude Code
/plugin marketplace add aetheria-labs1/storefront-skills
/plugin install lexsis-storefront-skills@lexsis

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

Tools each declares

The marketplaces of lexsis-storefront-skills publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of lexsis-storefront-skills publish no settings it asks for, so we do not compare settings.

What it can do: DevHub CMS · What it can do: lexsis-storefront-skills · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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