Changelog

MCP 2.0 changes what agents can do in Webflow and how. Most element, component, style, and variable operations no longer require a Designer session. This release also adds five new areas of functionality, expands several existing tools, and enforces your workspace’s permissions and audit logging across every agent action. Some tools and actions were renamed or relocated; see Migrating from an earlier version below.

Build without a Designer session

In earlier versions, working with elements, components, styles, and variables required an active Designer session through the Webflow MCP Bridge App. In 2.0, those capabilities work on their own:

• Query and edit the element tree: text, styles, links, images, attributes, tags, settings, visibility, and display names, plus moving and removing elements.
• Create, transform, and manage components, including instances, props, and variants.
• Create, update, rename, and remove styles (classes and combo classes), and manage per-style variable modes.
• Create, update, rename, and delete variables (color, font family, number, percentage, size), and build and reorder collections and modes.
• Build elements on a page from a schema, insert component instances (including nested trees), and insert elements from HTML and CSS.

None of these need a Designer session anymore.

New capabilities

MCP 2.0 opens up five areas of Webflow that agents couldn’t reach before. Each works without a Designer session.

Analyze reporting. Agents can work with Webflow Analyze data: pull traffic over a chosen window (sessions, users, or pageviews), rank a site’s top pages, break down leading values for a dimension like country, browser, or traffic source, surface the most frequent engagement events with page context, and read time on page as an aggregate or over time. Available for sites with Webflow Analyze.

Forms and submissions. Agents can read a site’s forms and their schemas, list and retrieve submissions (with optional element and locale filters), update the hidden fields on a submission, and delete submissions.

Custom fonts. Agents can list and inspect a site’s uploaded custom fonts, register and upload new font files, replace the file behind an existing font, update font metadata, and remove fonts individually or in batches.

Sitemap indexing. Agents can read, list, update, and bulk-update sitemap inclusion for CMS collection items and static pages.

Agent instructions. Agent instructions are markdown-based skills and rules that give agents custom guidance for working on a site. They can reference Webflow primitives like variables, styles, components, pages, CMS collections and items, and locales, and those references resolve against the site’s own data. In 2.0, these instructions are provided automatically to external agents, and agents can manage them directly: searching a site’s rules and skills, reading them (with referenced instructions resolved inline), and creating, updating, moving, renaming, and deleting them.

Expanded existing tools

Several existing capabilities gained new actions in 2.0:

• Pages: create a page, update settings across many pages at once, and read and bulk-update page schema markup and structured data.
• Assets: full asset and folder management (list, get, update, delete, and organize into folders), plus asset compression jobs with task tracking.
• Custom code: read and write the freeform custom code embedded at the site and page level, alongside existing registered-script management.

Still requires a Designer session

A few capabilities still depend on an active Designer session (through the Webflow MCP Bridge App):

• Element snapshots. Capturing a visual snapshot of an element, so an agent can read the current state of a site and verify its own changes before publishing.
• Selection and canvas navigation. Selecting and reading the selected element, navigating the canvas between pages and component views, reading the current page, mode, and branch, reading a site’s breakpoints, and creating page folders.
• Uploading an image from a URL. Adding an image to a site directly from a public URL.

Governance

MCP enforces your workspace’s permissions and roles, including custom roles: if a user can or cannot do something in the Designer, the same applies through MCP. Changes made by agents are recorded to the site audit log. This means you can give external agents site access while keeping the same permissions and audit trail as the rest of Webflow.

Migrating from an earlier version

Several tools and actions were renamed or relocated in 2.0, so skills, prompts, and automations written against an earlier version may call names that no longer resolve. A few examples:

• set_id is now set_dom_id, and add_or_update_attribute is now set_attributes.
• Element selection and canvas navigation moved to the dedicated Designer-session capabilities described above.
• Full asset and folder management moved off the image-upload tool, which now handles uploading an image from a URL only.

The skill migration guide lists every name that changed and what to replace it with. You can also point an agent at that page and have it update a skill on its own.

Known limitations

A few things to be aware of in this release:

• Element snapshots require a Designer session. Capturing a visual snapshot still depends on an active Designer session through the Webflow MCP Bridge App. If you want an agent to run independently, let it publish to a staging domain, which supports full agent loops without the Designer.
• One workspace per authorization. When you authorize the MCP server, you choose a single workspace it can access. To use a different workspace, reauthorize. In clients like Claude and ChatGPT, that means removing the connector and reinstalling it.
• Interactions (IX3) aren’t supported. Agents can’t create or apply Webflow Interactions through the MCP server. Build and edit interactions manually in the Designer.
• Custom fonts cover uploaded files only. The custom font capabilities manage font files you upload. Remotely hosted Google and Adobe Fonts are still managed manually in site settings. For Google Fonts, you can download the files and upload them through the MCP server.
• Some uploads require sending a file to a presigned upload URL. Uploading an asset, or uploading or replacing a custom font file, is a two-step flow: the tool returns a presigned upload URL, and the client sends the file’s bytes directly to that URL. If the client’s environment or network blocks that outbound request, the upload can’t complete. In that case, upload the file manually in Webflow instead.