DevHub CMS vs post-bridge
DevHub CMS is an MCP server published by devhub. Marketplaces we read that list it: 1 (Docker MCP Catalog). post-bridge is a plugin bundle for AI coding tools published by post-bridge-hq. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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 807 Stars (Docker Hub): 0 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.1.0 Forks (GitHub): 3 Stars (GitHub): 17 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 | post-bridge |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 9 (worse) | 17 (better) |
| Pulls (Docker Hub) (differs) | 17 807 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 (better) | 3 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/devhub-cms) | Remote server (www.post-bridge.com/api/mcp/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 2 | Not published |
| Parts of the bundle (differs) | Not a bundle | 4 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/devhub/devhub-cms-mcp | github.com/post-bridge-hq/agent-mode |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days 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.
post-bridge
Post to Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Pinterest, Threads, and Bluesky via Post Bridge 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-cms
Requires: DEVHUB_API_KEY (secret), DEVHUB_API_SECRET (secret)
post-bridge As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install post-bridge@claude-community
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only post-bridge has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of post-bridge publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of post-bridge publish no settings it asks for, so we do not compare settings.
What it can do: DevHub CMS · What it can do: post-bridge · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.