Changelog

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.

Update Page Metadata no longer returns an error when the slug field can’t be applied. The request now returns 200 OK with the slug field silently ignored — all other fields in the update apply as expected.

What changed

• Home pages, collection template (detail) pages, and utility pages (e.g. 404, password, search) previously returned 400 Bad Request ("Slug of index pages can't be updated", "Collection Template page slugs cannot be updated", or "Utility page slugs cannot be updated") when a slug was included. They now return 200 OK with the slug ignored.
• Secondary locales on sites without the Advanced or Enterprise Localization add-on previously returned 403 Forbidden when a slug was included. They now return 200 OK with the slug ignored.

Migration notes

If your integration relied on the previous 400 or 403 responses to detect page-type or plan restrictions, switch to comparing the returned page’s slug against the value you sent — they’ll differ when the slug was ignored.

You can now scope the List Assets endpoint (GET /v2/sites/{site_id}/assets) to return assets that are in a specified folder. In the same way, the response to this endpoint includes the folder that an asset is in.

New query parameter: folderId

Pass a folder’s ObjectId to receive only assets in that folder and all of its descendant folders. When folderId is omitted, the endpoint returns all assets on the site as before.

• Type: string (24-character hex ObjectId)
• Required: no
• Behavior: recursive — assets in nested subfolders are included
• pagination.total reflects the filtered count, so paginated UIs get correct totals

$
curl -H "Authorization: Bearer $WEBFLOW_TOKEN" \
>
  "https://api.webflow.com/v2/sites/$SITE_ID/assets?folderId=$FOLDER_ID"

New response field: folderId

Every asset in the response to this endpoint now includes a folderId field. The value is the ObjectId of the folder the asset belongs to, or null when the asset is at the site root.

1
{
2
  "assets": [
3
    {
4
      "id": "63e5889e7fe4eafa7384cea4",
5
      "displayName": "banner.png",
6
      "folderId": "6390c49774a71f99f21a08eb"
7
    },
8
    {
9
      "id": "63e5889e7fe4eafa7384cea5",
10
      "displayName": "logo.svg",
11
      "folderId": null
12
    }
13
  ]
14
}

Version 1.2.1 of the Webflow MCP server improves connection reliability and fixes compatibility with Gemini-based AI clients. If you are already using the MCP server, your agents and prompts automatically use this version.

Reliability

• Fixed connection drops: The MCP server now maintains open connections during idle periods instead of dropping them. Previously, agents could lose their session mid-task and require a full reconnect after a period of inactivity. Sessions now survive idle periods without interruption.

Bug fixes

• Gemini compatibility: Fixed an HTTP 400 error that prevented Gemini-based AI clients from using the element_builder and component_builder tools. Gemini’s strict OpenAPI 3.0 validation rejected array schemas that were missing an items type definition. Claude-based clients were unaffected.

Resources

• Getting started guide — Setup instructions
• How it works — Tool reference and capabilities
• Skills — Agent skills
• Prompt library — Example prompts

v1.21.0 adds a forms command group for reading form data and exporting submissions.

webflow forms list

Lists all forms on a site with their ID, display name, and slug. Supports --fields to customize columns and --json for machine-readable output.

$
webflow forms list --site <siteId>
$
webflow forms list --site <siteId> --json

webflow forms submissions

Lists all submissions for a specific form. Submissions can be output as a formatted table, JSON, or exported directly to CSV with --output.

$
webflow forms submissions --site <siteId> --form <formId>
$
webflow forms submissions --site <siteId> --form <formId> --output submissions.csv

Required OAuth scope: forms:read

v1.20.2 is a patch release with CMS UX improvements and a small auth output fix.

CMS error handling improvements

• Cleaner user errors — Invalid collection or item IDs now display a clean message and exit with code 1 instead of throwing a CLI error with a stack trace.
• Structured API error bodies — When the Webflow API returns an error, the full structured error body from the response is now included in the output, not just the HTTP status code.
• Next-steps hint after collections create — After successfully creating a collection, the CLI now prints a hint showing how to add fields to it:

  $
  webflow cms collections create --site <siteId> --name "Blog Posts"
  $
  # ✔ Collection created: Blog Posts (id: abc123)
  $
  # → Add fields: webflow cms fields create --collection abc123 --name <name> --type <type>

Fix: duplicate “Credentials saved” output

Running webflow auth login no longer prints the “Credentials saved” line twice. Previously, both ensureAuthenticated and the auth login command handler logged the message independently.

The Webflow AI Assistant can now generate and modify code components based on plain-language prompts. You can use the AI Assistant to generate visual and interactive components for your site, like custom sliders, pricing menus, calculators, The AI Assistant can access the styles and CMS collections from the current site and can make changes with further prompts.

For more information, limitations, and example prompts, see Quick start: Generating code components.

v1.20.1 is a patch release with two improvements.

cloud init updated to use devlink export

The webflow cloud init command now scaffolds projects using the new webflow devlink export command. The Astro and Next.js scaffold templates have been updated to take advantage of the latest DevLink features.

JSX default for DevLink component files

The deprecated webflow devlink sync command now defaults to generating component files with a .jsx extension instead of .js. You can still override the extension using the fileExtensions property in your webflow.json manifest file.

v1.19.0 adds webflow devlink export, a new command that generates a static, self-contained DevLink bundle of your Webflow components as local React code that runs without a build-time connection to Webflow.

webflow devlink export

$
webflow devlink export

Key features

• Filter exports — Use components and componentGroups regex patterns in webflow.json to control what gets exported.
• TypeScript or JavaScript — Output language is auto-detected from your project. Override with the ts option in webflow.json.
• CSS scoping — Optional CSS style isolation via cssScopes to prevent style leakage.
• Configurable output — Set the output location with rootDir, and rewrite link targets via relativeHrefRoot to fit any project layout.
• CI-friendly — Authenticate via OAuth interactively, or set WEBFLOW_API_TOKEN / --api-token for non-interactive use. Target a site with --site or via webflow.json.

Also in this release: code library selection in library share is now searchable and sorted alphabetically.

v1.20.0 introduces global session storage so a single webflow auth login covers all CLI commands, plus two new commands for inspecting and clearing your session.

Global session storage

Running webflow auth login now saves your credentials in two places:

• Global session file — ~/.config/webflow/auth.json on macOS/Linux or %APPDATA%\webflow\auth.json on Windows. This is shared across all projects and survives outside any specific project directory.
• Project .env file — WEBFLOW_API_TOKEN continues to be written for compatibility with existing 1.x workflows.

The WEBFLOW_API_TOKEN environment variable still takes precedence over the session file, so CI/CD pipelines that set it explicitly continue to work without changes.

New auth commands

• webflow auth status — Shows the currently authenticated user (name and email) and the active OAuth scopes for the stored token.
• webflow auth logout — Removes the global session file and logs you out of the CLI.

Version flag shorthand

The version flag has been changed from -V to -v for convenience.

$
webflow -v
$
# @webflow/webflow-cli/1.20.0