Ext Ops Panel
Open dashboard
Comparison

Webflow vs io.form/formio-mcp

Webflow is an MCP server published by webflow. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.form/formio-mcp is an MCP server published by form.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceWebflowio.form/formio-mcp
Docker MCP Catalog Listed
Version: sha256:20e73bbc57ed
Forks (GitHub): 36
Pulls (Docker Hub): 17 479
Stars (Docker Hub): 0
Stars (GitHub): 141
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (npm): 1 369
Downloads/week (npm): 549
Forks (GitHub): 4
Stars (GitHub): 8
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 io.form/formio-mcp
FactWebflowio.form/formio-mcp
Marketplaces that list it11
Stars (GitHub) (differs)141 (better)8 (worse)
Pulls (Docker Hub) (differs)17 479No figure on Docker Hub
Forks (GitHub) (differs)36 (better)4 (worse)
Last release (differs)Not published2026-10-14
Where it runs (differs)On your machine (mcp/webflow)On your machine (@formio/mcp)
Transportstdiostdio
Tools it declares (differs)21Not published
Environment variables it asks for (differs)1, secrets among them: 110, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/webflow/mcp-servergithub.com/formio/ai
Changes in the last 7 days (differs)03
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.

io.form/formio-mcp

In its own words, on Official MCP Registry:

Create and manage Form.io forms, resources, actions, roles, and projects from your AI agent.

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)

io.form/formio-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "FORMIO_API_KEY=<YOUR_FORMIO_API_KEY>" --transport stdio formio-mcp -- npx -y @formio/mcp

Requires: FORMIO_API_KEY (secret)

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

Tools each declares

The marketplaces of io.form/formio-mcp publish no list of tools, so we do not compare tools.

Settings each asks for

Only Webflow asks for

  • WEBFLOW_TOKEN (secret)

Only io.form/formio-mcp asks for

  • FORMIO_API_KEY (secret)
  • FORMIO_AUTH_HOST
  • FORMIO_AUTH_PORT
  • FORMIO_AUTH_TIMEOUT
  • FORMIO_BASE_URL
  • FORMIO_FORCE_BROWSER
  • FORMIO_INSECURE_TLS
  • FORMIO_LOGIN_FORM
  • FORMIO_PROJECT_URL
  • FORMIO_REQUEST_TIMEOUT

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

What it can do: Webflow · What it can do: io.form/formio-mcp · 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