Prefer English?
Prefer English? Switch the website language for a better experience.
Webflow keeps arming its MCP (Model Context Protocol), the gateway that lets AI agents like Claude, Cursor, or Codex directly operate a Webflow site. This new wave of features, announced in late September 2026, adds three major building blocks: interaction creation, faster CMS access, and full Webflow Cloud management.
In practice, agents connected via MCP can now:
In other words, the AI agent is no longer limited to reading or writing text content. It is now stepping into areas previously reserved for humans on the canvas: motion, animation, and application infrastructure.
Until now, Webflow MCP was mostly used to automate content tasks: publishing an article, updating a CMS field, generating a page. Useful, but limited. With this evolution, we are now touching much more sensitive topics: interaction design and app deployment.
Creating an IX3 interaction through an agent means replicating a move that used to require solid mastery of the Webflow Designer. Same goes for Webflow Cloud: being able to deploy and debug an app directly from an MCP client, without ever opening the Webflow interface, pushes the platform even closer to a genuine development environment that can be driven through natural language or code.
Branch management, meanwhile, clearly targets structured teams. Being able to merge, publish to staging, and check for conflicts before merging, all from an agent, is a real time-saver for production workflows with multiple contributors.
| MCP capability | Before this update | After this update |
|---|---|---|
| Interactions | Manual creation on the canvas only | Created via AI agent, based on IX3/GSAP |
| CMS | Limited queries, often multiple calls | Sort, filter, and paginate in a single query |
| Webflow Cloud | Deployment and debugging via the interface | Deployment, status, and debugging via MCP |
| Branches | Manual merge and staging management | Full cycle driven by agent (Enterprise) |
Yes, this update genuinely excites us. It marks a real shift: Webflow MCP no longer just pulls content, it now touches experience and technical architecture. For an agency like Mazette.co, that is a new string to our bow, provided the right guardrails are in place.
On interactions, we stay cautious but enthusiastic. An agent capable of suggesting a scroll trigger or a hover effect in a few seconds is a fantastic starting point. But animation, in Webflow, is also about feel, timing, and consistency with the brand. We will always keep reviewing, adjusting, and fine-tuning by hand what the AI proposes. The agent speeds up the draft, human expertise signs off on the final result. If animations are a topic you care about, we dig into it further in our article on the subtle art of breathing life into interfaces.
On the CMS side, this is concrete and immediately profitable. Filtering, sorting, and paginating in a single query is a game changer on sites with hundreds of entries, complex relationships between collections, or content migration needs. It saves precious time on tasks that used to require multiple back-and-forth API calls.
On Webflow Cloud, this might be the most strategic part. Being able to deploy and debug an app directly from an agent, without switching tools, confirms that Webflow is no longer just playing in the no-code space: the platform is seriously moving into the territory of full web applications. A trend worth watching closely for any agency supporting growing clients.
{{webflow}}Our stance has always been the same: AI is a fantastic copilot, never an autopilot without supervision. This kind of announcement reinforces our method, which combines execution speed with a demand for quality. MCP agents let us move faster on repetitive tasks, so we can spend more time on what really matters: strategy, design, and the business performance of your site.
If you are working with an agency that already masters the MCP ecosystem, this update will translate concretely into shorter turnaround times on content and CMS structuring tasks, without sacrificing the quality of interactions or technical robustness. If your site still runs on a legacy CMS, this is also a good opportunity to rethink your content architecture before migrating.
At Mazette.co, we follow these developments day in, day out to get the best out of them, without ever losing sight of what matters most: a site that converts, loads fast, and truly looks like your brand.
{{seo-aeo}}Code
Over 120 companies have already stepped out of the shadows with us.
Webflow MCP exposes the site API as a set of tools that agents like Claude, Cursor, or Codex can call directly. You connect the MCP server to your AI client, and the agent can then read or edit your CMS, create interactions, or run Webflow Cloud without going through the Designer interface.
Yes, the new version of MCP lets agents create and edit interactions based on IX3 and GSAP, using the same triggers as on the Designer canvas: scroll, hover, load, and click. That said, it remains an assistance tool, and human review is still essential to validate visual consistency and performance.
The classic Webflow API requires writing code for every call, while MCP provides an orchestration layer designed for AI agents, with ready-to-use tools. MCP simplifies access to the CMS, interactions, and Webflow Cloud without developers having to manually handle every request.
Impactful titles, polished meta descriptions, sitemaps, Schema.org, Hn structure, and audits: these are the SEO foundations that make your content readable by both Google AND generative AI. We cover both simultaneously.
With over 180 clients, our agency is one of the few in France to hold the Webflow Premium Partner label, supporting you in every area, including custom web design, sophisticated automation, conversion optimization, and SEO and GEO visibility.
We create bespoke web designs focused on performance, user journeys, and conversion. Join over 180 clients who have trusted us to elevate their brand.
