Ext Ops Panel
Open dashboard
Comparison

Webflow vs clay

Webflow is an MCP server published by webflow. Marketplaces we read that list it: 1 (Docker MCP Catalog). clay is a plugin bundle for AI coding tools published by clay-run. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Community GitHub marketplaces). 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
MarketplaceWebflowclay
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
Claude Code: claude-plugins-official Not listed Listed
Version: 2.26.0
Forks (GitHub): 22
Stars (GitHub): 134
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 clay
FactWebflowclay
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)141 (better)134 (worse)
Pulls (Docker Hub) (differs)17 443No figure on Docker Hub
Forks (GitHub) (differs)36 (better)22 (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
Hooks it runs (differs)Not published3
Parts of the bundle (differs)Not a bundle37
Licence (differs)MITNot stated
Repository (differs)github.com/webflow/mcp-servergithub.com/clay-run/agent-plugins
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.

clay

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

Work with Clay from Claude Code: set up and sign in to the clay CLI, query and analyze Clay tables, search Clay's GTM database for people and companies, manage audiences, signals, routines and workflows, and draft and review Sequencer campaigns. Includes hooks that auto-approve the plugin's own clay CLI calls and Clay skills; requires a Clay account.

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)

clay As a Claude Code plugin

Claude Code
/plugin install clay@claude-plugins-official

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

Tools each declares

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

Settings each asks for

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

What it can do: Webflow · What it can do: clay · 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-official/blob/HEAD/.claude-plugin/marketplace.json. 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