Webflow MCP: 9 Servers and Connectors Compared (2026)

A Webflow MCP server lets an AI assistant such as Claude, ChatGPT or a coding agent work on a Webflow site through the Model Context Protocol: build pages and components, manage the CMS, read analytics or publish a blog post from a chat instead of the Designer. Webflow runs an official server, and the name now also covers a beta server, a documentation server, community projects, hosted connectors, and tools such as Arvow that only publish content into a Webflow collection. This page compares nine of them by who makes them, what they can touch and what they cost. Facts come from each vendor's own documentation, repository or pricing page on November 10, 2026.

Webflow MCP servers compared

Server	Who makes it	Who it is for	What it does
Webflow MCP server	Webflow, official	Designers, marketers, developers	37 tools: design, CMS, pages, assets, SEO, analytics, governance
Webflow Beta MCP server	Webflow, official	Early adopters	Experimental tools and early-access API features
Webflow documentation server	Webflow, official	Developers	Searches Webflow's developer docs and API references
Arvow MCP	Arvow	Sites that want blog content	Writes SEO articles and publishes them to a Webflow collection
MCP Router	Kvalifik, open source	Agencies with several workspaces	One connection to many workspaces, permissions per project
webflow-mcp-server	kapilduraphe, open source	Self-hosters	Lists sites with a read-only token
Zapier Webflow MCP	Zapier	No-code users	Chosen Webflow actions through a hosted URL
Pipedream Webflow MCP	Pipedream	Developers	Webflow actions through one static URL
Composio Webflow toolkit	Composio	Developers and teams	Webflow actions with scoped access and an audit trail

Which Webflow MCP fits your job

The nine servers

1. Webflow MCP server: the official one

Webflow's own server runs remotely at mcp.webflow.com/mcp and authorizes with OAuth, so there is no API key to store. Its tool reference lists 30 data tools with 288 actions between them, three Designer tools with 17 actions, and four utility tools. An agent can build layouts, elements, styles, components, interactions and design variables; manage CMS collections, pages, assets, forms, sitemap settings and SEO metadata; and read Webflow Analyze, Optimize and AEO data, each an optional add-on on a paid site plan.

Webflow provides a Claude connector, a Webflow app in ChatGPT, a plugin for Grok Build (the client formerly called Cursor), and Postman and Slack integrations. Claude Code connects with one command, claude mcp add --transport http followed by a name and the server URL, and any other MCP client can use the URL directly. An MCP Bridge App installs during authorization and is only needed for work that depends on an open Designer session, such as visual snapshots; everything else runs through the Data API with the Designer closed, as the architecture page explains.

Governance is the part agencies will care about: every agent works within your existing Webflow permissions and roles, each site can carry Agent Instructions that the server hands to any connected agent, and the changes agents make are written to the site's activity log. The limits, from the same overview: one authorization covers one workspace, and switching means re-authenticating; the server cannot create a new site project; page branches need an Enterprise plan; it edits interactions built on GSAP but not Classic ones; it cannot create new localized CMS items; and Webflow Cloud deployments only work for apps connected to a GitHub repository. Only site owners and admins can authorize it, per the FAQ. The server itself costs nothing extra: Webflow's pricing page lists the Webflow AI MCP server on every site plan, including the free Starter plan, with Basic at $15 a month and Premium, the first plan with the CMS, at $25 a month, both billed yearly.

The same server runs locally from the open source package webflow-mcp-server (MIT license, 141 GitHub stars when we checked) with a Webflow API token and a Bridge App you publish in your own workspace.

2. Webflow Beta MCP server: tomorrow's tools

The Beta server at mcp.webflow.com/beta/mcp exposes experimental tools and early-access API features. The Claude connector and the Grok Build plugin point at the production server, so you add the beta one by hand, with the same Claude Code command or as a custom connector in Claude Desktop.

3. Webflow documentation MCP server: the docs inside your agent

Webflow also runs a documentation server under developers.webflow.com at /api/fern-docs/mcp. The main server already reads the documentation through it, so you only connect it directly when you want the docs without the site tools, for example while writing code against the Data API.

4. Arvow MCP: SEO content published to a Webflow collection

Arvow's MCP server is not a Webflow management server. It is here because this is our page, and because it covers the one job the others leave to you: writing the post. It has 49 tools for SEO work, from keyword research to LLM brand monitors. For Webflow, the relevant ones list the publishing integrations connected to your Arvow project and publish an article to one of them, either an article Arvow wrote or a title and HTML that the assistant passes in. The call waits up to 60 seconds and returns the status and the published URL.

The Webflow side is a site API token with read and write permission, created in Site Settings under Apps and Integrations. In the Arvow integration you pick the site, the collection (such as Blog Posts), the fields that receive the HTML body, the meta description and the featured image, and whether articles go live at once or arrive as drafts; the help article has the steps. The limits: it only writes to the collection you map, it cannot touch pages, styles or existing items, and it is a paid product. MCP access is listed from the Solo plan, from $39 a month billed yearly or $69 billed monthly, on arvow.com/pricing.

5. MCP Router: several workspaces through one connection

MCP Router is a free, open source desktop app for macOS and Windows by the agency Kvalifik. It connects projects across several Webflow workspaces through one MCP connection, with an access level per project, and one-click setup for Codex, Claude Desktop, Claude Code, Cursor, VS Code and Gemini CLI. It answers the official server's one-workspace-per-authorization rule, which is why it matters to agencies; its README states that it is not affiliated with Webflow.

6. webflow-mcp-server by kapilduraphe: the small community server

This MIT-licensed community server does one thing: its README lists two tools, get_sites and get_site, which return site details such as custom domains, locales and the last publish date. It needs only the sites:read scope, which makes it the safest option on the list and the least capable. It had 21 GitHub stars when we checked.

7. Zapier Webflow MCP: hosted actions, no code

With Zapier's Webflow MCP you generate an MCP URL, choose which Webflow actions the assistant may use, and connect it to your AI tool. The listed actions include Create Item, Create Live Item, Update Item, Update Live Item, Find Item, Fulfill Order and Update Order. There is nothing to host, and it runs through your Zapier account.

8. Pipedream Webflow MCP: one static URL for developers

Pipedream's Webflow MCP server uses one static URL, mcp.pipedream.net/v2, that works for every client; you authenticate when you add it. Its pricing page says development use is free with no credit card, while serving real users in production needs the Startup plan at $99 a month billed annually ($150 billed monthly) with 10,000 usage credits included, and a tool call through MCP uses a credit.

9. Composio Webflow toolkit: scoped access with an audit trail

Composio's Webflow toolkit is a hosted set of Webflow tools for agents, with scoped access and an audit trail of agent actions, usable from Claude, Codex, Cursor and its SDKs. Its pricing page lists a free plan at $0 with $2 in credits one time for up to 3 members, and a Standard plan at $18 per seat a month with $18 in credits per seat.

How to connect the official Webflow MCP server to each client

Client	How to connect	Note
Claude Desktop	Add the Webflow connector from the connectors list, or a custom connector with the server URL	You pick the sites or workspace to authorize
ChatGPT	Connect the Webflow app, then mention @Webflow in the chat	ChatGPT asks you to approve each action by default
Claude Code	One claude mcp add command, then /mcp to sign in	A project-scoped config gives each site its own folder
Grok Build (formerly Cursor)	Install the Webflow plugin, or add the URL to mcp.json	Also the way into the Beta server
Slack	Install the Webflow app from the Marketplace, then DM Slackbot or tag @Webflow	Slackbot is free and generally available; the @Webflow agent is in public beta
Postman	Connect from the Postman AI agent	For exploring the Data API

All six come from Webflow's getting started and Slack pages.

What a Webflow MCP server cannot do for a blog

Every server here moves content; none of them researches a keyword or writes the article. Webflow's skills page lists a Bulk CMS update skill and a CMS collection setup skill, and its prompt library has a keyword optimizer and an SEO metadata auditor, all acting on text that already exists. For a steady stream of posts, the pairing that works is Arvow to research and write, and Webflow's server or Arvow's integration to publish, the same split as in the WordPress MCP servers and the Shopify MCP servers we compared.

How to publish to Webflow from ChatGPT or Claude with Arvow

1. In Webflow, create a site API token with read and write permission, and connect it in Arvow as a Webflow integration, mapping the collection and fields. The help article has the steps.
2. In ChatGPT, create a custom connector with the URL https://api.arvow.com/mcp, choose OAuth and sign in. In Claude, add a connector with the MCP URL from your Arvow organization settings and your API key in an x-api-key header.
3. Ask: "List the integrations for this project, then publish my latest article to Webflow."

The full steps for each client are on the Arvow MCP page, and the Webflow writer itself on arvow.com/webflow.

FAQ

Is there an official Webflow MCP server?

Yes. Webflow runs it at mcp.webflow.com, documents it on developers.webflow.com, and publishes the local version as an open source package. It also runs a Beta server and a documentation server.

Is the Webflow MCP server free?

Webflow's pricing page lists the Webflow AI MCP server on every site plan, including the free Starter plan; the analytics, optimization and AEO data it reads are paid add-ons. The hosted alternatives have their own plans: Pipedream from $99 a month in production, Composio from $18 per seat. Arvow's MCP access starts at $39 a month billed yearly.

Does Webflow MCP work with ChatGPT and Claude?

Yes. Webflow provides a Webflow app in ChatGPT and a Claude connector, plus a Grok Build plugin and a Slack app, and any MCP client can connect to the server URL.

Can an AI assistant publish blog posts to Webflow?

Yes. The official server's CMS tool creates items as drafts and publishes them with a separate action. Arvow publishes through its Webflow integration, where you choose once whether articles arrive as drafts or go live, and adds the research and writing in front of it.

Does the Webflow MCP server need the Designer open?

Mostly no. Editing elements, styles and variables and managing CMS content, pages and assets work with the Designer closed. Only visual snapshots and reading or changing the current selection, page, mode, branch, canvas and breakpoints need the Designer open with the MCP Bridge App connected.