Ext Ops Panel
Open dashboard
Comparison

DevHub CMS vs BrewPage

DevHub CMS is an MCP server published by devhub. Marketplaces we read that list it: 1 (Docker MCP Catalog). BrewPage is a plugin bundle for AI coding tools published by kochetkov-ma. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-10. 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

Where each is published
MarketplaceDevHub CMSBrewPage
Docker MCP Catalog Listed
Version: sha256:d09cf1f01b09
Forks (GitHub): 13
Pulls (Docker Hub): 18 506
Stars (Docker Hub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed
Community marketplace davepoon/buildwithclaude Not listed Listed
Version: 0.1.0
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

DevHub CMS vs BrewPage
FactDevHub CMSBrewPage
Marketplaces that list it11
Stars (GitHub) (differs)9 (better)0 (worse)
Pulls (Docker Hub) (differs)18 506No figure on Docker Hub
Forks (GitHub) (differs)13 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/devhub-cms)Remote server (brewpage.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)10Not published
Environment variables it asks for (differs)3, secrets among them: 2Not published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Not statedMIT
Repository (differs)github.com/devhub/devhub-cms-mcpgithub.com/kochetkov-ma/brewpage-publish-plugins
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-08
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 33 h ago returned HTTP 405

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

In its own words, on Docker MCP Catalog:

DevHub CMS LLM integration through the Model Context Protocol.

BrewPage

In its own words, on Community GitHub marketplaces:

Publish HTML, Markdown, files and multi-file static sites from Claude Code to BrewPage and get an HTTPS link back, with no account or API key: a brewpage-publish skill plus the BrewPage remote MCP server (https://brewpage.app/mcp). Only content you ask it to publish is uploaded; links are unlisted but readable by anyone who has them (optional password), and content expires (15 days by default, 30 at most).

How to run each

DevHub CMS As a local MCP server: Docker image

Claude Code
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)

BrewPage As a Claude Code plugin

Claude Code
/plugin marketplace add davepoon/buildwithclaude
/plugin install brewpage@buildwithclaude

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only BrewPage has a remote endpoint we check. How we check endpoints

Tools each declares

Only DevHub CMS has

  • create_blog_post
  • get_blog_post
  • get_businesses
  • get_hours_of_operation
  • get_locations
  • get_nearest_location
  • site_from_url
  • update_blog_post
  • update_hours
  • upload_image

Only BrewPage has

  • bind_token
  • delete_resource
  • get_json
  • get_kv
  • get_limits
  • get_page
  • get_stats
  • mint_token
  • publish_file
  • publish_html
  • publish_json
  • publish_kv
Show the remaining 8
  • publish_site
  • republish_site
  • search_gallery
  • set_kv
  • set_visibility
  • update_hosting
  • update_html
  • update_json

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (BrewPage as of 2026-11-09). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of BrewPage publish no settings it asks for, so we do not compare settings.

What it can do: DevHub CMS · What it can do: BrewPage · 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.

Where the data comes from: how the catalog is built