Using Webflow MCP & Claude for "Poor Man's" Page Branching

Here is a workaround for Page Branching using Claude and the Webflow MCP. Page branching is a powerful Webflow Enterprise feature that allows you to experiment on a "forked" version of a page and merge changes back without breaking your global styles. The problem? It’s been locked behind a high-tier paywall since 2022, and even some "Enterprise Lite" plans don't have access to it. In this video, I demonstrate a "Poor Man’s Page Branching" workflow. By using Claude and the Webflow MCP, we can: Duplicate a page and automatically prefix every class name with a random 4-character string (e.g., T6HM-). Modify styles and elements in total isolation so they don't affect the rest of your site. Attempt to merge those changes back to the original page using AI comparison. ⚠️ Disclaimer: This is experimental technology! As seen in the video, it’s about 90% of the way there but still struggles with things like global components (navbars/footers) and complex merges. Key Takeaways: Keep your tab active: Webflow goes idle if it’s in the background, which breaks the MCP connection. Components workaround: My current theory is unlinking components on a blank "branch" page before running the prefix script. The Wait: It’s slow—plan to play some Steam Deck while the AI re-classes your elements!. Is Page Branching a feature Webflow should offer as a standalone add-on subscription? Let me know your thoughts on this approach in the comments! #Webflow #WebDesign #ClaudeAI #WebflowMCP #WebDevelopment #AIWorkflows