# Reported issues for Webflow

Pod holds 22 of 43 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [Webflow](/mcp/webflow-2).

## Most discussed

### data_cms_tool and data_pages_tool intermittently not registered by the MCP server

The Webflow MCP server intermittently stops exposing two specific tools — `data_cms_tool` and `data_pages_tool` — while every other data tool from the same server keeps working normally on the same connection and token. This blocks all CMS collection-item work (create/update/publish items). Per the docs, CMS content management is a supported capability, so this looks like a tool-registration bug rather than an unsupported feature.

## Environment

- **Client:** Claude Desktop (Cowork), connector

[Read the thread](https://github.com/webflow/mcp-server/issues/143) · 2026-07-10 · open · external user · 3 comments

### Randomly lost access to the CMS tool using claude with webflow connector mid session

I am using claude to build a website with Webflow.

Midway through a session, claude lost access to the CMS tool. 6 hours later still the same, tried disconnect and reconnect, tried restarting client, tried new chat session, tried restarting computer, tried allowing all permissions for the connector in settings.

Need help urgently.

[Read the thread](https://github.com/webflow/mcp-server/issues/140) · 2026-07-08 · open · external user · 3 comments

### Invalid JSON Schema: component_builder tool has array without items definition

## Bug Description

When using the Webflow MCP server with Factory Droid (and likely other MCP clients), the `component_builder` tool fails validation with:

```
Error: 400 Invalid schema for function 'webflow___component_builder': 
In context=('properties', 'actions', 'items', 'properties', 'component_schema', 'properties', 'slots', 'items', 'properties', 'children'), 
array schema missing items.
```

## Root Cause

The JSON Schema for the `component_builder` tool has a `children` field of type

[Read the thread](https://github.com/webflow/mcp-server/issues/116) · 2026-04-12 · closed · external user · 8 comments

### Designer tools broken since v1.2 deployment (April 1) — 'Unable to connect' despite Bridge App connected

## Description

Designer API tools (`element_tool`, `set_text`, `query_elements`) return "Unable to connect to Webflow Designer" since approximately April 1, 2026. The same setup worked perfectly on March 30.

Bridge App inside Designer shows **"Connected to MCP Server"** with green status. Read operations via Data API tools work fine. Only Designer write/query operations fail.

## Environment

- **MCP Config:** Remote server (`{"type": "http", "url": "https://mcp.webflow.com/mcp"}`)
- **Client:

[Read the thread](https://github.com/webflow/mcp-server/issues/108) · 2026-04-06 · open · external user · 20 comments

### Webflow MCP Bridge stuck on "Authorizing…" then "can't connect to MCP server" (Claude Desktop, no manual MCP config)

I'm consistently hitting a connection failure with the Webflow MCP Bridge App + Claude Desktop, even after clean reinstalls.

## Environment

- **OS:** macOS 26.3.1 (Mac mini, Apple Silicon)
- **Browser for Webflow Designer:** Chrome
- **Claude:** Claude Desktop (latest public build)
- **MCP setup:** Using built-in Webflow connector in Claude Settings > Connectors only. No manual `claude_desktop_config.json` MCP config. No `mcp-remote` setup.

## Steps to reproduce

1. Remove Webflow connector i

[Read the thread](https://github.com/webflow/mcp-server/issues/99) · 2026-03-26 · closed · external user · 10 comments

### element_builder times out permanently after ~35 minutes of sustained use

# Bug: element_builder times out permanently after ~35 minutes of sustained use

## Environment
- MCP Server: Webflow Designer MCP (via Claude Code CLI)
- Browsers tested: Chrome (latest), Safari (latest)
- OS: macOS
- Webflow Plan: Free/Starter
- Date: 2026-03-12

## Summary

The `element_builder` Designer tool works correctly for approximately 35 minutes of sustained use (~50 calls), then begins timing out permanently. No error code is returned — the call simply never resolves (spins indefinit

[Read the thread](https://github.com/webflow/mcp-server/issues/84) · 2026-03-12 · closed · external user · 3 comments

### Claude Desktop Remote MCP Server Configuration Documentation Error

# Claude Desktop Remote MCP Server Configuration Documentation Error

## Summary
The current Webflow MCP documentation instructs users to configure the remote server via `claude_desktop_config.json`, but **this method does not work with Claude Desktop**. Remote MCP servers must be added through the Claude Desktop UI (Settings > Connectors), not via the config file.

## Current Documentation Issue

**Location:** https://developers.webflow.com/data/docs/getting-started

**Current Instructions _(In

[Read the thread](https://github.com/webflow/mcp-server/issues/73) · 2025-12-18 · closed · external user · 3 comments

### Claude desktop over length limit when installing connector

As soon as I installed the webflow connector per the insturctions, all my Claude desktop conversations were over the length limit (even new ones where I just said "hi").  If you disable all tools the problem goes away - I started turning the tools on one by one and it worked until I did a big batch of tools at once.  There must be a problem where one tool is trying to pipe in an excessive amount of content to the chat.

[Read the thread](https://github.com/webflow/mcp-server/issues/58) · 2025-07-22 · closed · external user · 3 comments

## Most recent

### data_variable_tool: create/update_*_variable throws "An internal error occurred" for any custom_value CSS function expression (clamp/calc/color-mix)

## TL;DR

`data_variable_tool`'s `create_size_variable` / `update_size_variable` /
`create_color_variable` actions throw `"An internal error occurred"` whenever
`value.custom_value` is set to a CSS function expression (`clamp()`,
`calc()`, `color-mix()`) — including the schema's OWN documented examples
(`calc(100vh - 60px)`, `color-mix(in srgb, red 50%, blue)`). `static_value`
works fine on the same actions. The Designer UI/engine itself can store the
identical expression string on the same vari

[Read the thread](https://github.com/webflow/mcp-server/issues/146) · 2026-08-23 · open · external user · 0 comments

### [BUG] No write support for selectedItems component props.

# Webflow MCP: No write support for "selectedItems" component props

## Summary
The Webflow MCP server's Data API tools can **read** the value of a component instance prop typed `selectedItems` (a manually curated list of specific CMS item IDs), but there is **no supported way to write** a new value to that prop type. This blocks any MCP-driven workflow that needs to programmatically select specific CMS items into a component — e.g. choosing which blog posts appear in a "related posts" grid.

##

[Read the thread](https://github.com/webflow/mcp-server/issues/145) · 2026-08-20 · open · external user · 0 comments

### ask_webflow_ai always returns "Failed to fetch from FAI chat service" (both production and beta servers)

## Summary
The `ask_webflow_ai` tool consistently returns `{"error":"Failed to fetch from FAI chat service"}` for **any** input, and has been doing so for roughly a month. Every other MCP tool works normally in the same session, so this looks isolated to the FAI/AI chat backend that `ask_webflow_ai` proxies to — not a connection, auth, transport, or version issue.

## Reproduced on BOTH servers
- Production: `https://mcp.webflow.com/mcp`
- Beta: `https://mcp.webflow.com/beta/mcp`

Identical erro

[Read the thread](https://github.com/webflow/mcp-server/issues/144) · 2026-07-22 · open · external user · 0 comments

### `data_whtml_builder` silently creates duplicate styles, corrupting the Designer canvas while published output stays correct

## Summary

A single `data_whtml_builder` call that inserts two bare `<span>` elements into a Rich Text created **59 duplicate styles** site-wide. The published site remained pixel-correct, but the **Designer canvas and Preview were broken on every page** — all grid layouts collapsed. Because the published output was unaffected, the corruption was invisible to every normal verification step.

## Environment

- Webflow MCP Server (via Claude Code, `webflow-skills` plugin v1.0.6)
- Site built on t

[Read the thread](https://github.com/webflow/mcp-server/issues/142) · 2026-07-08 · open · external user · 0 comments

### Component property tools (de_component_tool / data_element_tool) not loaded in some sessions — can't create component properties

**Summary**
An agent using the Webflow MCP can create/define component properties in some sessions but not others. In an affected session, the tools that create or bind component properties (de_component_tool with get_component_instance_props, and data_element_tool) are never exposed, so there's no way to add a property to a component — even though the same action worked a day earlier on a different account/session.

**What I expected**
Be able to define a new component property (e.g. a text pro

[Read the thread](https://github.com/webflow/mcp-server/issues/141) · 2026-07-08 · open · external user · 1 comment

### MCP element writes return HTTP 406 "needs to reauthorize" on fresh OAuth grants; reads succeed (multiple clients)

Since July 7, 2026 (~11:00 AM PT), all element-level write operations through the Webflow MCP server (mcp.webflow.com/mcp) fail with HTTP 406 and the message "MCP needs to reauthorize. The Webflow MCP connection is no longer authorized," while read operations on the same connection succeed. Element writes on this site worked normally for the preceding weeks.
Affected: data_element_tool write actions (set_settings on an HtmlEmbed's code). Reads via the same tool (query_elements, get_settings) suc

[Read the thread](https://github.com/webflow/mcp-server/issues/139) · 2026-07-07 · open · external user · 1 comment

### Feature request: Replace an image in place in CMS Rich Text / Image fields (no delete-and-reinsert)

## Feature request: "Replace image" for an image already placed in a CMS Rich Text field (and CMS Image fields)

Today, once an image is inside a CMS Rich Text field, there is **no way to swap it in place**. To change it you must delete the whole figure and insert a new one — which shifts the surrounding text, drops the caption, and loses the alignment/float you had set. It is very easy to wreck the layout doing this, and for a client maintaining a blog it is a real, recurring pain.

### Ask
Let

[Read the thread](https://github.com/webflow/mcp-server/issues/138) · 2026-07-03 · open · external user · 0 comments

### Designer write tools return `ToolNotAvailable` despite appearing in tools/list — regression in 1.9.5 (prod + beta)

# Bug: Designer tools return `ToolNotAvailable` despite being listed in `tools/list` (prod + beta)

## Summary
Several Designer tools are advertised by `tools/list` but `tools/call` rejects them
with `ToolNotAvailable`, on BOTH production (`https://mcp.webflow.com/mcp`) and beta
(`https://mcp.webflow.com/beta/mcp`, serverInfo `webflow-mcp-beta` `1.9.5-beta`).
The Designer Bridge is confirmed connected (`designer_tool` works in the same
session), so this is NOT a Bridge / Build-mode / OAuth / Nod

[Read the thread](https://github.com/webflow/mcp-server/issues/136) · 2026-06-27 · closed · external user · 1 comment

### set_style applies the wrong class when a global class shares its name with a combo class (silently adds the combo's parent)

### Summary
`data_element_tool → set_style` accepts only `style_names: string[]` and resolves each name via an internal lookup. When a **global** class and a **combo** class share the same name — which happens automatically whenever a global class is stacked as a second class anywhere on the site — the bare name resolves to the **combo** Style object. `set_style` then expands that combo to its full chain, silently re-introducing the parent class. There is no way to target the global class specif

[Read the thread](https://github.com/webflow/mcp-server/issues/135) · 2026-06-26 · open · external user · 0 comments

### Designer MCP hangs on link-prop creation & leaves canvas parked in component view (bridge drops; needs manual 'back to page')

### Summary
When editing a **component** via the Designer MCP (through the Bridge App), some operations hang and never complete — the Bridge App shows the action as "Running…" with no green checkmark, and the bridge connection then drops. The two reliable triggers we hit:

1. **Creating a `link`-type component prop** (`create_prop` with `type: "link"`) hangs every time — it appears to open the link picker in the Designer and never returns.
2. After any component edit, the **canvas stays parked i

[Read the thread](https://github.com/webflow/mcp-server/issues/134) · 2026-06-18 · open · external user · 0 comments

### Designer Bridge reliability: background-tab "naps", write timeouts that actually land, and response overflows on heavier queries

# Designer Bridge reliability: background-tab "naps", write timeouts that actually land, and response overflows on heavier queries

**Reported by:** Claude (AI agent), filed on behalf of the account owner
**Date:** 2026-06-13
**Environment:** macOS 14 (Darwin 23.6.0), Google Chrome, Claude Code (MCP client), official Webflow MCP server + MCP Bridge App in the Designer
**Workload:** multi-week native rebuild of a marketing homepage (dozens of element/style writes per hour: `element_tool`, `style_

[Read the thread](https://github.com/webflow/mcp-server/issues/133) · 2026-06-12 · open · external user · 0 comments

### Too confident claim in tool description for `webflow_guide_tool`

The instruction 'ALWAYS CALL THIS TOOL FIRST' in the description is problematic. In multi-tool environments, it causes the model to trigger the tool unnecessarily, leading to significant token waste. I recommend updating the description with specific environment constraints to clarify when it is actually needed

[Read the thread](https://github.com/webflow/mcp-server/issues/128) · 2026-04-28 · open · external user · 0 comments

### In Chrome 147+, Bridge App self-hosting is blocked by LNA; needs iframe allow="loopback-network"

In [Chrome 147 and later](https://developer.chrome.com/release-notes/147#local_network_access_restrictions_for_websockets), [Local Network Access](https://developer.chrome.com/blog/local-network-access) (LNA) restrictions now apply to WebSockets. Normally, this just requires a permission prompt. But, for content in iframes – like the Webflow Designer Extensions – the iframe must also have `allow="loopback-network"` in order to attempt this at all.

If you self-host the Webflow MCP Bridge App **i

[Read the thread](https://github.com/webflow/mcp-server/issues/124) · 2026-04-21 · closed · external user · 1 comment

### `update_color_variable` rejects all `existing_variable_id` aliasing

## TL;DR

The Webflow MCP's `variable_tool` → `update_color_variable` action's `existing_variable_id` parameter always returns "not found," even when passed a variable ID that is demonstrably valid — including an ID currently in active use as a native alias elsewhere in the same site. Every combination tested (same-collection, cross-collection, Relume-seeded target, MCP-created target, solid-value target) fails. The same action's `custom_value` and `static_value` paths work correctly. Workaround

[Read the thread](https://github.com/webflow/mcp-server/issues/121) · 2026-04-15 · closed · external user · 1 comment