Webflow MCP + Cursor: the integration that truly changes the way you work
There comes a moment when you stop looking for excuses to open a browser tab while writing code. For many developers and designers working with Webflow, that moment arrived with the MCP integration in Cursor.
This is not just another automation feature. It represents a shift in perspective on what it means to work with a platform like Webflow when an AI agent becomes your direct intermediary.
MCP and why Webflow invested in it
The Model Context Protocol (MCP) is an open standard that allows AI agents to connect to external tools and act directly on them. Webflow has developed its own MCP server, publicly available, and made it compatible with Cursor, Claude Desktop, Windsurf, and other environments.
The core idea is simple but powerful: instead of searching through the Webflow API documentation, learning the right parameters, and writing calls manually, you describe what you want to do in natural language. The agent handles the rest.
Webflow had already released this MCP server some time ago. The recent development is the official launch of the plugin on the Cursor Marketplace, verified by the Cursor team, with one-click access and a library of ready-to-use skills. This step makes the integration accessible even to those who are not comfortable configuring MCP servers manually.
How to install it (spoiler: it's fast)
Open Cursor, go to
cursor.com/marketplace/webflow
and add the plugin.
Or directly inside the editor:
/add-plugin webflow
The first time the agent makes a call to Webflow, your browser opens for authentication, a process you only need to complete once.
Then you can test it with something simple:
“Show me my Webflow sites.”
If it returns the list of your sites, you’re ready to go.
A day with the plugin: what it actually changes
Here’s what a typical workday looks like for a team that uses the plugin on a daily basis.
In the morning, a SEO manager launches a site audit directly from Cursor. Within seconds, they get a full inventory: pages without meta descriptions, images missing alt text, broken links in the CMS. Tasks that used to take half a day manually.
In the afternoon, a developer updates 40 items in a product collection: a new category, new slugs, and a new “featured” field. They simply describe the change in natural language, and the agent shows a complete diff before applying anything. Nothing changes without validation.
At the end of the day, the safe-publish step lists everything that will go live: modified pages, CMS items still in draft. An explicit confirmation is required. The site is then published, and the agent checks that it is accessible.
It’s this loo, describe, preview, validate, act, that fundamentally changes the day-to-day workflow.
What you can do: the main skills
The plugin includes ten official skills. These are not isolated functions; they are complete workflows with preview, validation, and granular approval before each action. The agent never performs an operation without first showing you what it is about to do.
CMS content management
For teams using Webflow to manage content, the core of the integration is the ability to operate on the CMS directly from Cursor.
With bulk-cms-update, you can create or update dozens of items in a collection with a single instruction. The agent retrieves your collection schema, validates the data, shows you a preview with the differences (old → new), and waits for your confirmation before proceeding. A rollback system is built in: if you change your mind, you have a few minutes to undo everything.
With cms-collection-setup, you can create a new collection simply by describing the structure you need, including relationships. This is particularly useful when prototyping a site or adding new sections to an existing project.
cms-best-practices is a consultative skill. It guides you on the optimal structure for collections, when to use the CMS versus static content, and how to model relationships between different content types. It is especially valuable during the planning phase.
Site health and SEO
site-audit generates a complete inventory of the site: pages, collections, field schemas, missing SEO metadata, and draft items. It returns a snapshot of the site with a health score and prioritized recommendations. The report can be exported in Markdown, JSON, or CSV.
asset-audit analyzes images and files, identifies those without alt text or with non-optimized names for SEO, and proposes improved versions while validating each suggestion before applying it.
accessibility-audit requires connection to the Webflow Designer and performs a WCAG 2.1 compliance check: buttons without labels, inputs without associated labels, heading hierarchy issues, removed focus states, or touch targets that are too small. Each issue is presented with a proposed fix that can be applied individually.
link-checker scans all links across the site, static pages and CMS content, and flags broken links, links still using HTTP, and redirects that could be optimized.
Publishing and custom code
safe-publish introduces intentional friction into the publishing process: it shows everything that will go live, performs verification checks, and requires explicit confirmation. You must type “publish”, a generic “yes” is not enough. It then verifies that the site is accessible after publication. This deliberate friction helps prevent accidental deployments triggered by a casual response during a conversation with an AI agent.
custom-code-management allows you to add, view, or remove inline scripts such as tracking pixels, analytics snippets, or chat widgets. One limitation to note: deletion removes all existing scripts; selective removal is not currently supported via MCP.
The real value: not time saved, but better work quality
These tools are often presented mainly as time savers. And it’s true that auditing a hundred assets or updating fifty CMS items can be done in minutes instead of hours. But the most subtle value lies elsewhere.
When every action is preceded by a preview, when every change can be reversed, when the agent shows you what it is about to do before doing it, you work with far less hesitation. You test more, iterate more, and make mistakes with fewer consequences.
For teams managing Webflow sites in production, this quality of feedback before action is often more valuable than the time saved itself.
FAQ
Is the Webflow MCP plugin in Cursor free?
The plugin itself is free and available on the Cursor Marketplace. However, it requires an active Webflow account, and some features depend on your Webflow plan. Cursor also has its own independent pricing.
Do you need to know how to code to use this plugin?
No. CMS management, audits, and publishing features can be used through natural language without writing code. However, the skills related to Code Components or CLI are designed for more technical users.
What is the difference compared to Claude Desktop?
The MCP server is the same. The difference lies in the client environment and the available skills. Cursor organizes them as plugins in its Marketplace, while Claude Desktop, Windsurf, and other MCP clients access the same server but without pre-packaged skills.
Can you undo an action performed by the agent?
Some skills include a rollback system, especially bulk-cms-update and asset-audit, which allows you to revert changes for a few minutes after execution. For irreversible actions, the plugin always requires explicit confirmation before proceeding.
Where to start
The starting point is the Cursor Marketplace:
/add-plugin webflow
Authenticate once, then run a first test with a site audit or a CMS query.
You don’t need to know everything in advance. The best way to understand what this integration can do is simply to try it on something real — a site you already know, a collection you already manage — and observe how the agent interprets your instructions and proposes actions.
