Webflow MCP Server
Connect AI agents to your Webflow sites — manage CMS, pages, SEO, and publishing over MCP.
Updated
What is Webflow MCP?
The Webflow MCP server is a Model Context Protocol server that connects AI agents directly to your Webflow projects, exposing Webflow's APIs as tools an agent can call to manage CMS content, pages, SEO, assets, and publishing.
Webflow runs it as an official, fully-hosted remote server at https://mcp.webflow.com/sse, so there is nothing to deploy — your AI client connects over SSE and you authorize access through Webflow's OAuth login, selecting which sites the agent may touch. The same project is also open source on GitHub and can be self-hosted via npm if you prefer to run it yourself.
Once connected, an agent can work across Webflow's Data API (create and update CMS collections and items, manage pages and static content, publish sites and CMS items) and, with the Designer Bridge app open, the Designer API for building elements, styles, and components on the canvas. This makes it a practical backend for content localization, SEO updates, and publishing workflows driven by an LLM.
Connect the Webflow MCP server
Claude Code / Claude Desktop
- 1
Add the server to your MCP config
In Claude Desktop's mcpServers config (or via `claude mcp add` in Claude Code), add an entry named "webflow" with command `npx` and args `["mcp-remote", "https://mcp.webflow.com/sse"]`. Requires Node.js 22.3.0+.
- 2
Authorize via OAuth
Restart the client; an OAuth page opens. Sign in to Webflow and select the sites the agent may access.
- 3
Verify
Ask the agent to list your Webflow sites or collections to confirm the connection.
Uses the mcp-remote bridge to reach the hosted SSE endpoint; OAuth opens in your browser on first connect.
Cursor
- 1
Add the MCP server
In Cursor's MCP settings (mcp.json), add a "webflow" server with `"url": "https://mcp.webflow.com/sse"`.
- 2
Complete OAuth
Cursor opens a Webflow OAuth login automatically — authorize the sites you want the agent to manage.
- 3
Test it
Prompt Cursor to fetch a CMS collection or page to confirm the tools are available.
Cursor connects directly to the hosted SSE URL; no local bridge needed.
Sample use cases
Bulk-update and publish CMS collection items from approved content
Content lands in Webflow and goes live without manual copy-paste.
Update page SEO metadata and static content across a site
Consistent, agent-driven SEO edits applied at scale.
Localize and republish content into Webflow collections
Translated variants created and published programmatically.
Security & permissions
Authentication is OAuth: when you connect the remote server, Webflow opens an OAuth authorization page where you sign in and explicitly choose which sites the MCP server may access. The agent then acts with the permissions of the authorizing Webflow account against those sites — it can read and modify CMS collections and items, pages and content, assets, and trigger publishes. Grant only the sites you intend the agent to manage, and review the authorized connections in your Webflow account settings; the self-hosted option lets you keep tokens within your own infrastructure if required.
Using Webflow MCP with Gamut
In a Gamut workflow, the Webflow MCP server is wired in as a tool an agent calls on a schedule or in response to an event — for example, when new content is approved upstream, a Gamut agent can create or update the matching Webflow CMS items, refresh page SEO metadata, and publish the affected pages, all without a human in the loop. Gamut manages the OAuth connection and credentials so the agent simply invokes the Webflow actions it needs as part of a larger automation; the scope of what it can change is bounded by the sites you authorize.
Frequently asked questions
What is the Webflow MCP server?
It is Webflow's official Model Context Protocol server that connects AI agents to your Webflow projects, exposing Webflow's Data and Designer APIs as tools so an agent can manage CMS content, pages, SEO, assets, and publishing. It runs as a hosted remote server at https://mcp.webflow.com/sse.
Is the Webflow MCP server free?
Webflow provides the MCP server itself and its open-source repository at no additional charge, and it is governed by your existing Webflow account and plan. Webflow does not publish separate MCP pricing — usage is bounded by your normal Webflow plan and API limits. Check Webflow's current plans for specifics.
How do I connect the Webflow MCP server to Claude or Cursor?
For Claude, add an mcpServers entry using `npx mcp-remote https://mcp.webflow.com/sse` (Node.js 22.3.0+), restart, and complete the OAuth login. For Cursor, add a server in mcp.json with the URL https://mcp.webflow.com/sse and authorize the OAuth prompt. Then pick which sites the agent may access.
Is the Webflow MCP server hosted or self-hosted?
Both. Webflow hosts an official remote server at https://mcp.webflow.com/sse that requires no setup beyond OAuth, and the project is also open source on GitHub (github.com/webflow/mcp-server) so you can self-host it via npm if you prefer to run it in your own environment.