Changelog

This is an overview of the changes to the Webflow APIs and related tools. To filter the list, select one or more tags.

May 21, 2026

Interactions support in DevLink export

DevLink Component Export now ships interactions built with the new GSAP-powered Interactions engine. Animations defined on a component, including triggers, timelines, and GSAP plugins, are exported and run in your React project with no extra setup.

What’s exported

For every component that has Interactions, DevLink now emits:

  • Interaction registration code, wired through a new useIX3Interactions hook.
  • A per-export GSAP bundle (webflow_modules/devlink-gsap.js) that contains only the GSAP plugins your site actually uses, such as ScrollTrigger, SplitText, and CustomEase. Plugin dependencies such as CustomBounce → CustomEase and ScrollSmoother → ScrollTrigger are resolved automatically.
  • The IX3 runtime bundle (webflow_modules/devlink-ix3.js) that initializes GSAP and registers interaction data.

GSAP plugin selection is driven by the site itself. No CLI flag or configuration is needed.

One provider, both engines

The <DevLinkProvider> component now wraps both Classic Interactions (IX2) and the new GSAP-powered Interactions (IX3). There is no separate <IX3Provider> component to compose:

1import { DevLinkProvider } from './devlink/DevLinkProvider';
2import { AnimatedHero } from './devlink/AnimatedHero';
3
4export default function App() {
5  return (
6    <DevLinkProvider>
7      <AnimatedHero />
8    </DevLinkProvider>
9  );
10}

Existing Classic Interactions setups keep working unchanged.

Lazy by default

The IX3 runtime and GSAP bundle load on demand, only after a component that uses useIX3Interactions mounts. Sites that don’t use interactions, and pages that don’t render an animated component, pay zero runtime cost: nothing is fetched and the bundles are never executed.

Framework support

  • Next.js (App Router and Pages Router, both Webpack and Turbopack): works in dev (StrictMode safe) and production builds.
  • Vite, Rollup, and esbuild: dynamic import specifiers are statically analyzable, so chunks are emitted cleanly.
  • Astro: works inside React islands. As with any React context provider, place a single client:load directive on the wrapping component. Two separate client:load islands won’t share IX3 context.

Requirements

  • @webflow/webflow-cli v1.19.0 or later
  • Node.js v22 or later

To use

Update your Interactions so that they are scoped to the component that you’ll export. Then re-run the webflow devlink export command to pick up IX3 animations from your site. No changes are needed in the webflow.json file.

For more information, see What’s exported.

May 21, 2026

MCP v1.3: Components, branching, and expanded authoring tools

Version 1.3 of the Webflow MCP server adds over 30 new tools and actions across component authoring, branch management, styles, elements, and comments. If you are already using the MCP server, your agents and prompts automatically use this version. To start using the MCP server, see Getting started.

Components

Agents can now work with components end-to-end. They can create blank components, define and manage props, set and reset prop values on instances, bind props to element settings and text, manage variants (including variant-scoped style variable modes), duplicate components, reorder variants, and unlink component instances. They can now read and edit Text and Rich Text prop content. In many cases they can set CMS field bindings as component props.

Component query results are now richer: responses can include props, instance counts, and variants. Library components and code components (with their read-only and runtime flags) are now included in component lookup results.

Branching

Agents can now create, inspect, and delete page branches. They can retrieve branch details and IDs for the currently active page.

Styles

Agents can now query styles by ID, name path (including combo classes), and CSS properties, with options to include breakpoint and property data. They can create and update styles from raw CSS.

Elements

Agents can now query elements using a range of filters (ID, type, text content, style, tag, attributes, component name, and slot), delete elements from the canvas, and reposition elements relative to an anchor without deleting and recreating them. The element builder now supports a much broader set of element types, including rich text, form elements, media embeds, tabs, sliders, CMS collections, page slots, and dropdowns.

Comments

Agents can now read and add site comments: listing threads and replies, replying to threads, and looking up workspace users by email. Comments at the element level are also now supported.

CMS

Agents can now unpublish CMS items.

Mode awareness

Agents now understand which Designer mode the user is in. The current mode is exposed in tool responses, ModeForbidden errors are surfaced clearly, and tool descriptions include mode constraints to prevent unnecessary failures. Guide content has been updated for Build mode workflows.

MCP resources

The MCP server now supports MCP resources. In supported clients such as Claude and Cursor, you can @-reference resources directly without calling a tool first. The Webflow Guide is now available as a resource.