Webflow Studio

The website guy stopped answering emails in October. Before that, he was slow. Before that, he was fine. Now you own a Webflow site you didn't build and you're afraid to touch it, and the homepage still says "Book your Spring 2024 appointment."

Webflow's official MCP server is the thing that gives you back custody of your own site. It connects Claude to your Webflow workspace with real read-and-write access to your CMS collections, collection items, site content, and SEO fields. You describe the change in English. Claude edits the CMS item. You publish.

This is narrow and specific. It's not for designers building a site from scratch — Webflow's own visual editor is still where that happens, and it's good. It's for the person who inherited a finished site and needs to maintain it: update the team page when someone leaves, add a new case study, change a price, fix a typo on the about page that's been bothering them for eight months.

There are two audiences it's built for. The first is small-business owners whose "website guy" has gone ghost. The second is solo designers and freelancers maintaining five or ten client sites — the kind of work where every minute of CMS data-entry is a minute you don't bill for, and offloading it to Claude means you can take on a sixth client without losing your weekends.

Where it's weak: it does not redesign sections, it does not build new page templates, it does not replace the Webflow Designer for structural work. If the thing you need is "make it look different," you still need to open Webflow.

One specific joy: the bulk content work. Adding twelve blog posts, each with hero image, excerpt, tags, and SEO title? That's a one-sentence ask now.

If you know someone who's been avoiding their Webflow site for months because editing it feels like disarming a bomb, send them this. It's the permission slip they needed.