Ext Ops Panel
Open dashboard
Comparison

Webflow vs decocms-studio

Webflow is an MCP server published by webflow. Marketplaces we read that list it: 1 (Docker MCP Catalog). decocms-studio is a plugin bundle for AI coding tools published by decocms. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-20. 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
MarketplaceWebflowdecocms-studio
Docker MCP Catalog Listed
Version: sha256:20e73bbc57ed
Forks (GitHub): 36
Pulls (Docker Hub): 17 546
Stars (Docker Hub): 0
Stars (GitHub): 141
Not marked · First seen
Not listed
Community marketplace decocms/studio Not listed Listed
Version: 1.0.3
Forks (GitHub): 56
Stars (GitHub): 410
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 decocms-studio
FactWebflowdecocms-studio
Marketplaces that list it11
Stars (GitHub) (differs)141 (worse)410 (better)
Pulls (Docker Hub) (differs)17 546No figure on Docker Hub
Forks (GitHub) (differs)36 (worse)56 (better)
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 bundle1
Licence (differs)MITNot stated
Repository (differs)github.com/webflow/mcp-servergithub.com/decocms/studio
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-15

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.

decocms-studio

In its own words, on Community GitHub marketplaces:

Operate a deco Studio organization (chats, agents, tools, files) from any agent through the decocms CLI and your own login.

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)

decocms-studio As a Claude Code plugin

Claude Code
/plugin marketplace add decocms/studio
/plugin install decocms-studio@decocms

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

Tools each declares

The marketplaces of decocms-studio publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Webflow · What it can do: decocms-studio · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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