
Webflow MCP server
online · 100% uptimeWebflow MCP Pack
not scanned yet
0 stars
Reviews
Write oneNobody has reviewed Webflow yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Webflow tools
Tool list not cached yet. `describe` through the gateway fetches it live.
How Webflow compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 77/100
- higher than 50% of 48,273 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 100 ms
- faster than 83% of 30,037 servers
Release history: 4 versions in the registry since 2026-06-03, latest 2026-10-29, typically one every 32 days.
Install Webflow in Claude Code, Cursor or VS Code
claude mcp add --transport http webflow https://gateway.pipeworx.io/webflow/mcp
What the publisher says
From the Webflow repository's README, as published. We do not edit it. Read it on GitHub
mcp-webflow
Webflow MCP Pack
Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.
Tools
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"webflow": {
"url": "https://gateway.pipeworx.io/webflow/mcp"
}
}
}What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/webflow/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1679+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.
No MCP client? Call it over HTTP
This pack runs against a connected webflow account, so it needs a Pipeworx key: sign in at https://pipeworx.io/account, connect webflow, then call POST https://gateway.pipeworx.io/v1/tools/listsites with Authorization: Bearer . Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/listsites. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"webflow": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-webflow"]
}
}
}Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Webflow: common questions
- Is Webflow MCP server safe?
- Mostly: it is graded B (77/100). Read the Webflow safety report
- How do I install Webflow?
- It runs remotely at gateway.pipeworx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Webflow need an API key?
- Yes. The registry entry asks for
PIPEWORX_API_KEY. - Is Webflow maintained?
- The last commit was 38 days ago (2026-09-25). The latest release is v0.2.0.
- Is Webflow up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Webflow compare with other MCP servers?
- safety score 77/100 (higher than 50% of 48,273 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 100 ms (faster than 83% of 30,037 servers). Full comparison.