The Webflow plugin in Cursor: manage your CMS without leaving the editor

Webflow joins the Cursor marketplace

Webflow just announced news that will speak directly to technical teams: its integration is now available as a plugin in the Cursor marketplace, the AI powered code editor. One single command, /add-plugin webflow, and you get Webflow’s MCP server plus ten ready-to-use agent skills in a single move.

In practice, this means Cursor’s AI agent can now talk directly to your Webflow site: read its content, audit it, edit it, and even publish it, all without opening your browser or juggling between two tools.

What this plugin actually does

The MCP (Model Context Protocol) server acts as the technical bridge between the Cursor agent and Webflow’s Data and Designer APIs, with OAuth authentication. It sets up the connection. The agent skills, on top of that, frame specific use cases:

• Bulk CMS updates, with validation and a diff preview before anything is applied
• WCAG 2.1 accessibility audits covering buttons, forms, links, headings and keyboard navigation
• Asset audits to spot missing alt text and file names that are not SEO friendly
• CMS collection setup and schema review
• Secure publishing, with a confirmation step before anything goes live

The MCP server and agent skills are published as open source under the MIT license. For the full list of available tools and installation details, head to the official MCP server documentation.

Why Webflow is betting on Cursor

This release confirms a deeper trend at Webflow: making the platform controllable from the tools teams already work in, rather than forcing them back into the Webflow interface for every task. We had already seen this logic at play with control via Google Gemini, and the arrival in Cursor follows the same direction: less context switching, more actions happening right where the code (and now the AI agent) is doing the work.

{{webflow}}

{{seo-aeo}}

Mazette.co’s take

At Mazette.co, we welcome this news with real enthusiasm, and not just out of early adopter reflex. What we like here is that Webflow is not simply opening a technical door: it is structuring it. The agent skills are not mere shortcuts, they frame sensitive actions (bulk content edits, publishing) with validation steps. That is exactly the kind of discipline we apply ourselves on every client project.

The built in accessibility audit and asset audit particularly resonate with us: these are checks we systematically run before every production release, often by hand or with separate tools. Seeing them embedded directly into developers’ workflow, right as they code, changes the game in terms of execution speed.

Our only reservation: the real value of this integration depends heavily on the technical maturity of the team using it. For a small structure without a developer using Cursor day to day, the impact will remain limited. But for an agency or a product team that already lives in Cursor, this is a genuine gain in fluidity, and one more proof that Webflow takes its role as an open platform seriously, rather than a walled garden.

Whether your site already runs on Webflow or you are considering a migration, this kind of tooling deserves to be factored into how your team will work tomorrow.