Ext Ops Panel
Open dashboard
Comparison

Webflow vs Blog Automation

Webflow is an MCP server published by webflow. Marketplaces we read that list it: 1 (Docker MCP Catalog). Blog Automation is an MCP server published by shsoftwaresolutioncom. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
MarketplaceWebflowBlog Automation
Docker MCP Catalog Listed
Version: sha256:20e73bbc57ed
Forks (GitHub): 38
Pulls (Docker Hub): 17 956
Stars (Docker Hub): 0
Stars (GitHub): 141
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.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

Webflow vs Blog Automation
FactWebflowBlog Automation
Marketplaces that list it11
Stars (GitHub) (differs)141 (better)0 (worse)
Pulls (Docker Hub) (differs)17 956No figure on Docker Hub
Forks (GitHub) (differs)38 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/webflow)Remote server (mcp.blog-automation.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)21Not published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/webflow/mcp-servergithub.com/shsoftwaresolutioncom/blog-automation-mcp
Changes in the last 7 days (differs)42
First seen (differs)2026-10-112026-11-07
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

Webflow

In its own words, on Docker MCP Catalog:

Model Context Protocol (MCP) server for the Webflow Data API.

Blog Automation

In its own words, on Official MCP Registry:

Write blog articles with AI and publish them to WordPress, Shopify and 30+ platforms.

How to run each

Webflow As a local MCP server: Docker image

Claude Code
claude mcp add --env "WEBFLOW_TOKEN=<YOUR_WEBFLOW_TOKEN>" --transport stdio webflow -- docker run -i --rm -e WEBFLOW_TOKEN mcp/webflow

Requires: WEBFLOW_TOKEN (secret)

Blog Automation As a remote MCP server

Claude Code
claude mcp add --transport http blog-automation-mcp https://mcp.blog-automation.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: BA_API_KEY (secret), Authorization header

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

Tools each declares

The marketplaces of Blog Automation publish no list of tools, so we do not compare tools.

Settings each asks for

Only Webflow asks for

  • WEBFLOW_TOKEN (secret)

Only Blog Automation asks for

  • BA_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Webflow · What it can do: Blog Automation · 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.

Where the data comes from: how the catalog is built