DevHub CMS vs HasData Shopify
DevHub CMS is an MCP server published by devhub. Marketplaces we read that list it: 1 (Docker MCP Catalog). HasData Shopify is an MCP server published by hasdata.com. 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
| Marketplace |  DevHub CMS |  HasData Shopify |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:d09cf1f01b09 Forks (GitHub): 12 Pulls (Docker Hub): 17 798 Stars (Docker Hub): 0 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.3 Downloads/month (npm): 664 Downloads/week (npm): 40 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
| Fact | DevHub CMS | HasData Shopify |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 (better) | 8 (worse) |
| Pulls (Docker Hub) (differs) | 17 798 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/devhub-cms) | Remote server (mcp.hasdata.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/devhub/devhub-cms-mcp | github.com/hasdata/shopify-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 10 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
DevHub CMS
DevHub CMS LLM integration through the Model Context Protocol.
HasData Shopify
The public product catalogue and collections of any Shopify storefront, as structured JSON.
How to run each
DevHub CMS As a local MCP server: Docker image
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-cmsRequires: DEVHUB_API_KEY (secret), DEVHUB_API_SECRET (secret)
HasData Shopify
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: HASDATA_API_KEY (secret), x-api-key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only HasData Shopify has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of HasData Shopify 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 HasData Shopify asks for
HASDATA_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: DevHub CMS · What it can do: HasData Shopify · 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.