Webflow vs PublishQ
Webflow is an MCP server published by webflow. Marketplaces we read that list it: 1 (Docker MCP Catalog). PublishQ is an MCP server published by publishq.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  Webflow | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:20e73bbc57ed Forks (GitHub): 38 Pulls (Docker Hub): 17 925 Stars (Docker Hub): 0 Stars (GitHub): 141 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published 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 | Webflow | PublishQ |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 141 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 17 925 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 38 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/webflow) | Remote server (publishq.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 21 | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/webflow/mcp-server | Not stated |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-04 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 31 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
Webflow
Model Context Protocol (MCP) server for the Webflow Data API.
PublishQ
Schedule and publish posts, organize media into folders, and keep each brand in its own workspace.
How to run each
Webflow As a local MCP server: Docker image
claude mcp add --env "WEBFLOW_TOKEN=<YOUR_WEBFLOW_TOKEN>" --transport stdio webflow -- docker run -i --rm -e WEBFLOW_TOKEN mcp/webflowRequires: WEBFLOW_TOKEN (secret)
PublishQ As a remote MCP server
claude mcp add --transport http publishq https://publishq.com/mcpRequires: PUBLISHQ_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only PublishQ has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of PublishQ publish no list of tools, so we do not compare tools.
Settings each asks for
Only Webflow asks for
WEBFLOW_TOKEN (secret)
Only PublishQ asks for
PUBLISHQ_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: PublishQ · 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.