FAQs and troubleshooting

Common questions and solutions for installing, configuring, and using the Webflow MCP server.

Installation and setup

After installing the MCP server, you may need to restart your AI client to see the new server. Additionally, check that your client (Claude Desktop, Cursor, or Windsurf) is updated to the latest version.

Troubleshooting steps:

  1. Restart your AI client completely
  2. Check for updates to your AI client
  3. Verify the MCP server configuration is correct in your config file
  4. Review the getting started guide for platform-specific instructions

Each authorization grants access to a single workspace. To switch to a different workspace, re-authenticate the MCP server:

  • Connector and app-based clients (such as Claude and ChatGPT): Remove the Webflow connector or app, then reinstall it and authorize the workspace you want.
  • Other clients: Remove the Webflow MCP server from your client’s configuration, then add it again to start a new authorization.

When the authentication screen appears, choose the workspace you want the MCP server to access.

Only site owners and admins can authorize the MCP server and MCP Bridge App. If you’re not a site owner or admin, you won’t be able to authorize those sites.

To resolve this:

  • Request owner or admin access from your site administrator
  • Or, have a site owner/admin authorize the MCP server for the site

Using the MCP server

Some capabilities need a live Designer session — capturing visual snapshots, and reading or changing the current selection, page, mode, branch, canvas, and breakpoints. To use these, open the MCP Bridge App in the Webflow Designer:

Steps:

  1. Open your site in the Webflow Designer
  2. Press the E key to open the Apps panel
  3. Launch the “Webflow MCP Bridge App”
  4. Wait for the app to connect to the MCP server

The MCP Bridge app must remain open in the Webflow Designer for these capabilities to work. You can minimize it after it connects.

If the MCP server times out or disconnects while using the Designer, your browser may be putting inactive tabs to sleep. Configure your browser to keep the Designer tab active:

Chrome:

  1. Go to chrome://settings/performance
  2. Scroll to “Always keep these sites active”
  3. Click “Add” and enter webflow.com

Firefox:

  1. Type about:config in the address bar
  2. Search for browser.tabs.unloadOnLowMemory
  3. Set to false
  4. Or keep the Designer tab pinned to prevent unloading

Safari:

  1. Safari doesn’t have a built-in setting for this
  2. Keep the Designer tab active and pinned
  3. Or use Chrome/Firefox for better MCP server stability

Pinning the Webflow Designer tab in any browser can also help prevent timeout issues.

The MCP server currently supports a focused set of Data and Designer API tools. Not all Webflow API endpoints are available through the MCP server.

Request new tools:

Most of the time, no. Creating and editing elements, components, styles, and variables, and managing CMS content, pages, assets, and other site data all work without the Webflow Designer open.

You need the Webflow Designer open, with the Bridge App launched and connected, only for capabilities that depend on a live Designer session:

  • Capturing visual snapshots of elements
  • Reading or changing the current selection, page, mode, and branch
  • Navigating the Designer canvas and reading the site’s breakpoints

The agent called a tool that the current mode does not allow.

To resolve this:

  • Switch to the Designer mode that the tool requires; tool descriptions in the MCP server list the modes in which each tool can run
  • Ask the agent to retry the action after you switch modes
  • For canvas changes, make sure that you are in Build mode and that the Bridge App is connected

The MCP server has partial support for localization:

Supported:

  • Read and update static page/component content in secondary locales
  • Read and update default component properties in secondary locales
  • Read and update existing CMS items in secondary locales

Not supported:

  • Creating new localized CMS items

If you need additional localization features, please open an issue or contact developers@webflow.com.