WEBFLOW

🟠 Webflow's Claude integration decided to play hide-and-seek with some tools on Desktop—web and CLI versions still work like they actually know what they're doing. Team's 'actively investigating,' which is corporate for 'we found the bug in the last place we looked.'. (Auto-resolved: no updates in 24h)

⏰ Jul 08, 2026 Fixed (for now) spotted via status_rss

// The official story

Reports of some missing tooling from the Webflow MCP Server

// Status page says

Jul 8 , 13:50 UTC Update - We've identified that this issue is impacting the Claude Desktop app, where some MCP Server tools may be unavailable. As a workaround, customers can continue using the Webflow MCP Server through the web-based version of Claude or the Claude CLI while we work to resolve the issue. Our team is actively investigating and we'll share another update as soon as we have more information. Tha

🔗 Official status page (for the PR-approved version)

https://status.webflow.com/incidents/xfkjg1vw4y8j

Webflow's Greatest Hits

⚪ WEBFLOW Sep 28, 2026

⚪ Webflow's publishing speeds went full sloth mode for a hot minute, then engineers threw spaghetti at the wall and declared victory. Sites are live again, customer patience rewarded with a participation trophy.

⚪ WEBFLOW Sep 28, 2026

🟡 Webflow customers discovered their sites publish at geological timescales. Engineers deployed a fix and claim victory, though 'monitoring closely' is tech speak for 'fingers crossed.' Apparently deployment speed and reliability are mutually exclusive concepts.

⚪ WEBFLOW Sep 22, 2026

⚪ Forms kept working, webhooks kept humming, but notification emails decided to ghost users for nearly two days. The emails have been revived and are awkwardly apologizing to your inbox.

⚪ WEBFLOW Sep 22, 2026

⚪ 📧 Webflow briefly decided notification emails were optional. Forms still worked, webhooks still fired, but your customers' inbox notifications took an unscheduled vacation. Now resolved, and yes, they're monitoring it like a hawk.