Ext Ops Panel
Open dashboard
Comparison

Webflow vs MainWP

Webflow is an MCP server published by webflow. Marketplaces we read that list it: 1 (Docker MCP Catalog). MainWP is an MCP server published by mainwp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceWebflowMainWP
Docker MCP Catalog Listed
Version: sha256:20e73bbc57ed
Forks (GitHub): 36
Pulls (Docker Hub): 17 443
Stars (Docker Hub): 0
Stars (GitHub): 141
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.5.0
Downloads/month (npm): 1 738
Downloads/week (npm): 1 006
Forks (GitHub): 6
Stars (GitHub): 28
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 MainWP
FactWebflowMainWP
Marketplaces that list it11
Stars (GitHub) (differs)141 (better)28 (worse)
Pulls (Docker Hub) (differs)17 443No figure on Docker Hub
Forks (GitHub) (differs)36 (better)6 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/webflow)On your machine (@mainwp/mcp)
Transportstdiostdio
Tools it declares (differs)21Not published
Environment variables it asks for (differs)1, secrets among them: 13, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/webflow/mcp-servergithub.com/mainwp/mainwp-mcp
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.

MainWP

In its own words, on Official MCP Registry:

Manage WordPress sites in MainWP from AI tools, with approval before destructive changes by default.

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)

MainWP As a local MCP server: npm package

Claude Code
claude mcp add --env "MAINWP_APP_PASSWORD=<YOUR_MAINWP_APP_PASSWORD>" --env "MAINWP_URL=<YOUR_MAINWP_URL>" --env "MAINWP_USER=<YOUR_MAINWP_USER>" --transport stdio mainwp-mcp -- npx -y @mainwp/mcp

Requires: MAINWP_APP_PASSWORD (secret), MAINWP_URL, MAINWP_USER

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

Tools each declares

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

Settings each asks for

Only Webflow asks for

  • WEBFLOW_TOKEN (secret)

Only MainWP asks for

  • MAINWP_APP_PASSWORD (secret)
  • MAINWP_URL
  • MAINWP_USER

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

What it can do: Webflow · What it can do: MainWP · 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