Webflow MCP Server – Visual Site Design and CMS

Overview

Webflow's official MCP server connects compatible AI agents directly to
authorized Webflow sites. It translates natural-language requests into
supported Webflow Designer API and Data API operations, allowing an agent to
work with live site structure, design data, content, and configuration instead
of relying only on screenshots, exported code, or manually copied CMS records.

What the MCP server enables

The server exposes tools for visual design, content management, site data, and
workflow automation. Depending on the authenticated user's permissions and the
available Webflow tools, an AI agent can:

• Create responsive sections, containers, grids, and other layout structures.
• Query, add, reposition, update, or delete supported elements on the canvas.
• Create and update styles, classes, CSS properties, variables, and breakpoint behavior.
• Build components, manage props and variants, and update component instances.
• Create and manage page branches for isolated design changes.
• Work with CMS collections and items, pages, assets, custom code, scripts, and site metadata.
• Retrieve Webflow guidance and structured project context through MCP resources.

When to use it

Use Webflow MCP when an agent needs live access to a Webflow project or must
perform authorized design and content changes. Typical workflows include
creating a responsive landing-page section, refactoring styles, building a
reusable component, updating CMS content in bulk, reviewing site structure,
managing assets or scripts, and preparing changes on a page branch before
publishing or human review.

Connection and authentication

Webflow hosts the production MCP server at https://mcp.webflow.com/mcp over
Streamable HTTP. The connection uses Webflow OAuth, including token refresh, so
users do not need to place API keys in the MCP configuration. Only site owners
and admins can authorize sites for the server.

Clients that require a local stdio bridge can use mcp-remote to connect to the
same hosted endpoint. Webflow requires Node.js 22.3.0 or later when using that
package. OAuth authorization also installs the Webflow MCP Bridge App on the
selected sites.

Key considerations

Designer API operations require the Webflow Designer to be open and the MCP
Bridge App to remain launched and connected; Data API operations do not require
the Designer to be open. The server exposes a focused subset of Webflow's APIs,
not every endpoint. It cannot manage site or Workspace access, and it cannot
create new localized CMS items, although it can read and update supported
existing localized content. Tool availability can also depend on the active
Designer mode. Limit authorized sites, review write operations, and use page
branches or human approval for high-impact design and content changes.