Webflow MCP Server

About

Webflow's official MCP server exposes the Webflow Data API — CMS collections, pages, custom code, assets, and site publishing — to AI coding tools and to Webflow's own AI-assisted Designer workflow. The recommended path is Webflow's hosted remote server at mcp.webflow.com/sse: add it to Cursor, Claude Desktop (via the `mcp-remote` bridge), or another MCP client, authenticate with OAuth against your Webflow workspace, then open the "Webflow MCP Bridge App" from the Designer's Apps panel (press E) to sync your live canvas with the AI agent in real time — letting you ask it to analyze recent blog posts for new topic ideas, add internal links between related posts, or build out a new hero section with a responsive CTA. Teams that want a fully self-hosted setup can instead register their own Webflow Bridge App with Admin permissions and run the open-source `webflow-mcp-server` npm package locally (`npx -y webflow-mcp-server@latest`) with a scoped WEBFLOW_TOKEN, giving full control over the OAuth flow and hosting. The server requires Node.js 22.3.0+ for the remote/local hybrid flow. Under the hood it's generated from Webflow's OpenAPI spec via Fern, so it tracks new Data API endpoints automatically as Webflow ships them. Typical use cases lean CMS-heavy: bulk content edits, SEO audits across blog collections, and automating repetitive Designer tasks that would otherwise mean clicking through the visual builder by hand.

Installation

npx -y webflow-mcp-server@latest (local) — or connect to https://mcp.webflow.com/sse (remote, OAuth)

Categories

Works With

Frequently Asked Questions

Related Guides