DevHub CMS vs Brand Rep
DevHub CMS is an MCP server published by devhub. Marketplaces we read that list it: 1 (Docker MCP Catalog). Brand Rep is a plugin bundle for AI coding tools published by b-open-io. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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 |  Brand Rep |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:d09cf1f01b09 Forks (GitHub): 12 Pulls (Docker Hub): 17 820 Stars (Docker Hub): 0 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Community marketplace b-open-io/claude-plugins | Not listed | Listed Version: 0.1.10 Forks (GitHub): 4 Stars (GitHub): 16 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 | Brand Rep |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 (worse) | 16 (better) |
| Pulls (Docker Hub) (differs) | 17 820 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 12 (better) | 4 (worse) |
| 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 | Not published |
| Parts of the bundle (differs) | Not a bundle | 3 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/devhub/devhub-cms-mcp | github.com/b-open-io/prompts |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
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.
Brand Rep
Personas for public-facing surfaces that answer customers rather than developers. Optional module for core.
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)
Brand Rep As a Claude Code plugin
/plugin marketplace add b-open-io/claude-plugins
/plugin install brand-rep@b-open-ioCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Brand Rep publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Brand Rep publish no settings it asks for, so we do not compare settings.
What it can do: DevHub CMS · What it can do: Brand Rep · 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.