DevHub CMS vs SEO Content Machine
DevHub CMS is an MCP server published by devhub. Marketplaces we read that list it: 1 (Docker MCP Catalog). SEO Content Machine is a plugin bundle for AI coding tools published by SEO Content Machine. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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 | |
|---|---|---|
| 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 |
| Community marketplace gitterebi/seo-content-machine-plugin | Not listed | Listed Version: 1.1.0 No figure published 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 | SEO Content Machine |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 17 798 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/devhub-cms) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | 2, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/devhub/devhub-cms-mcp | github.com/gitterebi/seo-content-machine-plugin |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-13 |
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.
SEO Content Machine
Drive the SEO Content Machine desktop app from Claude Code: scraping, site crawls, Google Maps listings, archive.org downloads and SEO Workspace pages.
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)
SEO Content Machine As a Claude Code plugin
/plugin marketplace add gitterebi/seo-content-machine-plugin
/plugin install seo-content-machine@seo-content-machineCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of SEO Content Machine 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 SEO Content Machine asks for
SCM_API_KEY (secret)SCM_API_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: DevHub CMS · What it can do: SEO Content Machine · 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.