Webflow vs Tengence GEO Agent
Webflow is an MCP server published by webflow. Marketplaces we read that list it: 1 (Docker MCP Catalog). Tengence GEO Agent is an MCP server published by tengence.com. 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
| Marketplace | ||
|---|---|---|
| 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: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 0 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 | Tengence GEO Agent |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 141 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 17 443 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 36 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/webflow) | On your machine (@tengence/geo-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 21 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 3, secrets among them: 0 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/webflow/mcp-server | github.com/tengence-team/tengence-geo-agent |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
Model Context Protocol (MCP) server for the Webflow Data API.
Tengence GEO Agent
GEO/SEO content pipeline MCP: plan, write, gate-check, publish, submit, monitor AI visibility.
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)
Tengence GEO Agent As a local MCP server: npm package
claude mcp add --transport stdio geo -- npx -y @tengence/geo-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Tengence GEO Agent publish no list of tools, so we do not compare tools.
Settings each asks for
Only Webflow asks for
WEBFLOW_TOKEN (secret)
Only Tengence GEO Agent asks for
DB_DRIVERSITES_ROOTTENGENCE_GEO_HOME
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Webflow · What it can do: Tengence GEO Agent · 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.