Changelog

Webflow MCP Server Version Update to 0.5.1

Feature enhancements

• Inline script management
  Use AI agents to generate and insert (or delete) inline code snippets

• Collection Item deletion
  Agents can now remove CMS items programmatically, completing the full CRUD through your AI coding tool.

Improvements

• Structural refactor
  The codebase now has a clearer folder structure, consistent naming, and easier long-term maintenance.** No breaking changes.**

New tools

These updates give your AI agents deeper, safer autonomy:

Add 0.5.1 your AI editor

See our MCP server documentation for more information on how to add the MCP server to your AI editor.

1
{
2
  "mcpServers": {
3
    "webflow": {
4
      "command": "npx",
5
      "args": ["-y", "webflow-mcp-server@0.5.1"],
6
      "env": {
7
        "WEBFLOW_TOKEN": "<YOUR_WEBFLOW_TOKEN>"
8
      }
9
    }
10
  }
11
}

Workspace audit logs and improvements for Webflow Apps

Introducing workspace audit logs

To enable better security and compliance monitoring, the Webflow Data API now supports workspace-level audit logs for enterprise customers. In combination with the existing site-level audit logs, teams now have a complete view of user activity across their organization.

Use the Workspace Audit Log API to track important user events, including:

• Login activity
• Custom role events
• Workspace membership events
• Site membership events
• Workspace invitations

Localization support for additional elements

These updates enable you to localize more element types on a page. In addition to the existing support for text-based elements and component instances, you can now localize the following elements using the Page APIs:

• Select choices on a select element
• Placeholder text on a text input element
• Button text on submit and search buttons

Quality of life updatesWebflow Apps

Additionally, Webflow Apps now supports:

1. Inviting users to test apps
   You can now invite external users to test your apps before publishing to the marketplace by simply providing their email address and a message. This feature addresses the previous limitation where in-development apps could only be installed within the registered workspace. Contact developers@webflow.com for early access.

2. Safeguarding app settings for marketplace apps
   We’ve improved stability for marketplace apps by implementing safeguards against breaking changes. To protect both app developers and end users, certain critical setting changes for published apps now require re-approval through our update process. This ensures your users always have a consistent experience while giving you a controlled path to evolve your app’s capabilities. In your app settings modal, you’ll now see some disabled settings that require re-approval to make changes.

   These settings include:

   • Adding a new building block (Designer or Data API)
   • Changing app scopes

Introducing Webflow’s official MCP server and LLMS.txt support

Introducing Webflow’s MCP server

For developers using AI-powered tools like Cursor or Claude Desktop, we provide a Model Context Protocol (MCP) server that enhances the agent’s understanding of your Webflow projects. The MCP server has tools that enable the AI agent to access real-time information about your sites, collections, and other objects, enabling more accurate and contextual code suggestions and troubleshooting. To see a full list of tools, see the MCP server documentation.

LLMS.txt support

We’re excited to announce compatibility with the emerging llms.txt standard, making your documentation accessible and optimized for AI developer tools such as Cursor, GitHub Copilot, ChatGPT, Perplexity, and Anthropic’s Claude.

llms.txt is designed to be token-efficient, ensuring faster processing and cost-effective LLM interactions without sacrificing valuable info. Learn more

• Use https://developers.webflow.com/llms.txt to access the LLM-readable documentation.
• Additionally, you can access markdown versions of any documentation page to provide a more structured and context-rich experience for LLMs. To access the markdown version of a page, add .md to the end of the URL.

Comments API and enhanced form controls

Webflow is excited to introduce a new Comments API. With these new endpoints, you can programmatically access comments across your Webflow sites, enabling integrations with your existing tools and workflows. This release makes it easier than ever to track feedback, coordinate reviews, and streamline your content management processes.

• List all comment threads
• Get comment thread
• List comment replies
• Create webhook with a new comment_created trigger
• New comment thread webhook

Add .well-known files to your site

In addition to existing support for site configuration, the Data API now supports setting and deleting .well-known files. This empowers site managers to automate and streamline the management of site metadata and security configurations, enhancing integration with modern web protocols and improving overall site interoperability. For more information, see Wefblow’s help documentation on .well-known files.

• Set .well-known file
• Delete .well-known file

Support for option fields

• Create Option fields
  Option fields let you define a predefined list of choices for a collection item. You can add these fields either when creating a new collection via the create collection endpoint or add them to existing collections using the create collection field endpoint.

Improved control over form submission data

The List form submissions by site endpoint now lets you retrieve form submissions across your entire site. Unlike the existing List Form Submissions endpoint, this endpoint:

• Takes siteId as a path parameter
• Accepts elementId as a query parameter to filter by formElementId
• Works seamlessly with forms in components, where each component instance gets a unique formId but shares the same formElementId

To use this endpoint, first get the formElementId from the List Forms API, then pass both the siteId and formElementId to retrieve all submissions for a specific form, even when it appears in multiple component instances.

Enhancements to CMS fields and site configuration

The Data API now supports creating reference fields and creating multiple fields during collection creation.

• Create reference fields
  To create a reference field, choose MultiReference or Reference as the type property in the field object. Additionally, include the metadata property to specify the collectionId of the collection that the reference field will point to. You can create a reference field during collection creation using the create collection endpoint or by updating an existing collection using the create collection field endpoint.
• Create fields during collection creation
  You can now create multiple fields during collection creation using the create collection endpoint. Collections are limited to 60 fields per collection.

Add and manage robots.txt

• Configure robots.txt.
  Use the following endpoints to get and update your robots.txt file:
  • Get robots.txt
  • Replace robots.txt
  • Update robots.txt
  • Delete robots.txt

Tracking publishing history and deleting form submissions

Track publishing history

Track publishing history for a site using the lastPublished parameter. This parameter returns the date and time of the last published version of a site’s custom domain. This parameter will appear in the response for the get custom domains endpoint, as well as the list sites and get site endpoints.

Delete form submissions

Delete form submissions from a site using the delete form submission endpoint.

JavaScript SDK updates

Version 3.1.0 is now available and up to date with the latest changes in the Data API v2.

301 redirects, workspace management, and CMS publishing improvements

The Data API now supports programmatic management of 301 redirects and workspace administration, alongside enhanced bulk CMS operations in the JavaScript SDK. These additions enable developers to automate site configuration tasks and streamline content management workflows through new endpoints and improved functionality.

New site configuration capabilities

301 redirect management

Take control of your site’s 301 redirects with new endpoints that let you create and manage 301 redirects programmatically:

• List 301 redirects
  Get all configured 301 redirects for a site

• Create 301 redirect
  Add a new 301 redirection rule

• Update 301 redirect
  Modify an existing 301 redirection rule

• Delete 301 redirect
  Remove an existing 301 redirection rule

Workspace management

Programmatically create, update, and delete sites within your workspace:

• Create site
  Create a new site in your workspace

• Update site
  Modify an existing site’s properties

• Delete site
  Remove a site from your workspace

Improved CMS operations

Bulk CMS management

The Data API now supports efficient methods to perform operations on multiple CMS items at once:

• Create multiple items
  Create single or multiple CMS items in one request

• Update multiple items
  Update multiple CMS items simultaneously

• Update multiple live items
  Update multiple published CMS items

• Delete multiple items
  Unpublish/delete multiple CMS items at once

• Delete multiple live items
  Unpublish/delete multiple published CMS items

Breaking changes in JavaScript SDK: December 17, 2024 release

This document outlines the breaking changes introduced in the December 17, 2024 release of the Webflow Data API and JavaScript SDK. Review these changes carefully as they may require updates to your existing implementations.

Breaking changes in JavaScript SDK

Collection management

• Changed method name for deleting collections

  1
  // Old
  2
  client.collections.deleteCollection()
  3
  4
  // New
  5
  client.collections.delete(collectionId)

• New method for deleting collection fields

  1
  client.collections.deleteField(collectionId, fieldId)

CMS item creation

• Changed: client.collections.createItems() replaces previous methods
• Removed: client.collections.createItemForMultipleLocales()

Pages localization

• Changed parameter name: The locale query parameter is now localeId

Migration guide

Deleting collection items

If you’re using the existing collection deletion method, update your code to use the new method name:

1
// Before
2
await client.collections.deleteCollection(collectionId);
3
4
// After
5
await client.collections.delete(collectionId);

Collection item creation

Replace any usage of the deprecated methods with the new unified method:

1
// Before (deprecated)
2
await client.collections.createItemForMultipleLocales(collectionId, {
3
  localeIds: [primaryCmsLocaleId, secondaryCmsLocaleId],
4
  // other params
5
});
6
7
// After
8
await client.collections.items.createItems(collectionId, {
9
  cmsLocaleIds: [primaryCmsLocaleId, secondaryCmsLocaleId],
10
  isArchived: false,
11
  isDraft: false,
12
  fieldData: {
13
    // your fields here
14
  },
15
});

Page localization

Update any code that queries localized pages to use the new parameter name:

1
// Before
2
const pages = await client.pages.list({ locale: "507f1f77bcf86cd799439011" });
3
4
// After
5
const pages = await client.pages.list({ localeId: "507f1f77bcf86cd799439011" });

If you encounter any issues with these changes, please contact our support team for assistance.

SDK improvements

• Type improvements

  • Removed requirement for id in request payloads when creating resources
  • fieldData type in CMS Items now allows arbitrary key/value pairs, supporting custom fields

• Flexible CMS item creation The SDK now allows creation of CMS items with custom fields without requiring type updates