DevHub CMS vs PlanVortex
DevHub CMS is an MCP server published by devhub. Marketplaces we read that list it: 1 (Docker MCP Catalog). PlanVortex is an MCP server published by taliasoftworks. 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
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:d09cf1f01b09 Forks (GitHub): 12 Pulls (Docker Hub): 17 787 Stars (Docker Hub): 0 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.11.1 Forks (GitHub): 0 Stars (GitHub): 0 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 | PlanVortex |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 17 787 | 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) | On your machine (planvortex-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | 6, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/devhub/devhub-cms-mcp | github.com/taliasoftworks/planvortexmcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
DevHub CMS LLM integration through the Model Context Protocol.
PlanVortex
Schedule posts, read comments and answer messages across all your social networks.
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)
PlanVortex As a local MCP server: npm package
claude mcp add --env "PLANVORTEX_CLIENT_ID=<YOUR_PLANVORTEX_CLIENT_ID>" --env "PLANVORTEX_CLIENT_SECRET=<YOUR_PLANVORTEX_CLIENT_SECRET>" --transport stdio planvortex -- npx -y planvortex-mcpRequires: PLANVORTEX_CLIENT_ID, PLANVORTEX_CLIENT_SECRET (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of PlanVortex 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 PlanVortex asks for
PLANVORTEX_CLIENT_IDPLANVORTEX_CLIENT_SECRET (secret)PLANVORTEX_MCP_ALLOW_AIPLANVORTEX_MCP_READ_ONLYPLANVORTEX_MCP_UPLOAD_DIRSPLANVORTEX_ORGANIZATION_ID
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: DevHub CMS · What it can do: PlanVortex · 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.