DevHub CMS vs ABOVO.co — Email-to-Web Publishing
DevHub CMS is an MCP server published by devhub. Marketplaces we read that list it: 1 (Docker MCP Catalog). ABOVO.co — Email-to-Web Publishing is an MCP server published by seanfenlon. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  DevHub CMS |  ABOVO.co — Email-to-Web Publishing |
|---|---|---|
| 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 |
| Official MCP Registry | Not listed | Listed Version: 1.1.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 | ABOVO.co — Email-to-Web Publishing |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 18 066 | 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 (https://github.com/seanfenlon/abovo-mcp-server/releases/download/v1.1.1/abovo-mcp-server-1.1.1.mcpb) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | 5, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/devhub/devhub-cms-mcp | github.com/seanfenlon/abovo-mcp-server |
| 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.
ABOVO.co — Email-to-Web Publishing
Publish content to the web by emailing . No API key, no signup. SMTP is the API.
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)
ABOVO.co — Email-to-Web Publishing
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: ABOVO_SMTP_PASS (secret), ABOVO_SMTP_USER
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of ABOVO.co — Email-to-Web Publishing 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 ABOVO.co — Email-to-Web Publishing asks for
ABOVO_SENDER_EMAILABOVO_SMTP_HOSTABOVO_SMTP_PASS (secret)ABOVO_SMTP_PORTABOVO_SMTP_USER
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: DevHub CMS · What it can do: ABOVO.co — Email-to-Web Publishing · 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.