Webflow MCP Server

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.

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.

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.