Ext Ops Panel
Open dashboard
Comparison

Webflow vs editorial-os

Webflow is an MCP server published by webflow. Marketplaces we read that list it: 1 (Docker MCP Catalog). editorial-os is a plugin bundle for AI coding tools published by EditorialOS. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-13. 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
MarketplaceWebfloweditorial-os
Docker MCP Catalog Listed
Version: sha256:20e73bbc57ed
Forks (GitHub): 36
Pulls (Docker Hub): 17 453
Stars (Docker Hub): 0
Stars (GitHub): 141
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 1.0.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

Webflow vs editorial-os
FactWebfloweditorial-os
Marketplaces that list it11
Stars (GitHub) (differs)141 (better)0 (worse)
Pulls (Docker Hub) (differs)17 453No figure on Docker Hub
Forks (GitHub) (differs)36 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/webflow)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)21Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle17
Licence (differs)MITNot stated
Repository (differs)github.com/webflow/mcp-servergithub.com/editorialos/editorial-os
Changes in the last 7 days00
First seen2026-10-112026-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

Webflow

In its own words, on Docker MCP Catalog:

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

editorial-os

In its own words, on Claude Code: claude-plugins-community:

Content strategy, competitive analysis, editorial calendars, content drafting, email subject lines, and social repurposing — all from one Google Drive folder. Seven commands, five skills, one workflow. Built from 20 years of editorial operations at WIRED, Amazon, Sunset, and the Los Angeles Times.

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)

editorial-os

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Tools each declares

The marketplaces of editorial-os publish no list of tools, so we do not compare tools.

Settings each asks for

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

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