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 error on both.
Steps to reproduce
- Connect the Webflow MCP server (Claude Desktop native remote connector, macOS).
- Call
ask_webflow_ai with any message, e.g. { "message": "test connectivity" }.
- Response is always:
{"error":"Failed to fetch from FAI chat service"}
Expected
A normal AI answer about the Webflow API.
Actual
{"error":"Failed to fetch from FAI chat service"} — every call, on both the production and beta servers.
Scope / isolation
Everything else on the same connector is healthy in the same session, which points at the ask_webflow_ai → FAI chat service hop specifically:
data_sites_tool → list_sites returns all sites successfully.designer_tool, data_component_tool, data_component_props_tool, data_element_tool, data_scripts_tool, data_pages_tool all work — used them to add a component property, bind it, and DevLink-export, with no errors.
So the MCP server, OAuth handshake, and bridge app are all fine; only this one tool's backend fetch fails.
Environment
- Client: Claude Desktop, native remote MCP connector (macOS)
- Servers:
mcp.webflow.com/mcp and mcp.webflow.com/beta/mcp
- webflow CLI 2.2.0 (unrelated to the remote tool; included for completeness)
Notes
Duration ~1 month. Possibly adjacent to the recent "missing tooling from the Webflow MCP Server" incidents (status.webflow.com, 8 and 16 July 2026), though this presents differently: the tool is present and callable, but its downstream fetch to the FAI chat service fails, rather than the tool being absent.
Summary
The
ask_webflow_aitool 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 thatask_webflow_aiproxies to — not a connection, auth, transport, or version issue.Reproduced on BOTH servers
https://mcp.webflow.com/mcphttps://mcp.webflow.com/beta/mcpIdentical error on both.
Steps to reproduce
ask_webflow_aiwith any message, e.g.{ "message": "test connectivity" }.{"error":"Failed to fetch from FAI chat service"}Expected
A normal AI answer about the Webflow API.
Actual
{"error":"Failed to fetch from FAI chat service"}— every call, on both the production and beta servers.Scope / isolation
Everything else on the same connector is healthy in the same session, which points at the
ask_webflow_ai → FAI chat servicehop specifically:data_sites_tool → list_sitesreturns all sites successfully.designer_tool,data_component_tool,data_component_props_tool,data_element_tool,data_scripts_tool,data_pages_toolall work — used them to add a component property, bind it, and DevLink-export, with no errors.So the MCP server, OAuth handshake, and bridge app are all fine; only this one tool's backend fetch fails.
Environment
mcp.webflow.com/mcpandmcp.webflow.com/beta/mcpNotes
Duration ~1 month. Possibly adjacent to the recent "missing tooling from the Webflow MCP Server" incidents (status.webflow.com, 8 and 16 July 2026), though this presents differently: the tool is present and callable, but its downstream fetch to the FAI chat service fails, rather than the tool being absent.