Connecting Claude to Webflow

Webflow just launched an official Claude connector. For the Webflow community, professionals and the organizations they serve, this is worth paying attention to.

I've been working with Claude directly in Webflow for a while now. Not experimenting with it casually, but building it into real project work: updating CMS collections, rewriting content at scale, managing SEO metadata, restructuring field architecture across entire sites. A recent session covered 28 blog posts, a multi-reference field migration across 13 portfolio items, a new case study, and an About page rewrite, without opening the Designer once for any of the CMS work.

The official connector formalizes what practitioners have been figuring out on their own. Here's what I've learned about how it actually works, and where the line still sits between what Claude handles and what requires a Webflow professional.

What the Connector Actually Is

The Webflow Claude connector is a first-party integration that gives Claude direct access to your Webflow site through the Designer. It's built on Webflow's MCP Server, which means Claude has defined, structured tools, not open-ended API access. It knows how to create and update CMS collections, manage classes and variables, apply custom attributes, work with comments, and more.

The result is a workflow where Claude can move from strategy to execution inside Webflow, rather than stopping at suggestions you then have to apply yourself.

The Workflow in Practice

Here's how sessions actually run:

1. Set the context first. Before touching any content, Claude gets the brand guidelines, voice notes, and relevant examples. In Claude's Projects feature, this context persists across conversations, so no re-briefing every session.
2. Draft and iterate together. Copy gets written in conversation, with pushback and refinement until it's right. The judgment call, does this actually sound like them, stays with the professional.
3. Review before anything goes live. Claude pushes to Webflow as a draft. You review. You publish. AI handles execution; you handle editorial judgment.
4. Push directly from Claude. Once approved, Claude updates CMS items field by field, publishes, archives, manages slugs, all without switching to the Webflow interface. For bulk work especially, this compounds quickly.

What Claude Handles Well

After real project work, here's where Claude earns its place in a Webflow workflow:

Bulk CMS updates across large collections. Content rewrites that hold consistent voice across dozens of items. CMS architecture, creating collections, adding fields, setting up multi-reference relationships. SEO metadata reviewed and rewritten at scale across an entire site. Publishing, archiving, and slug management handled programmatically rather than one at a time.

For any Webflow professional managing content-heavy sites, the time savings on these tasks are significant. Work that used to mean an afternoon in the CMS can happen in a focused session.

What Still Needs You

This is the part most AI workflow posts skip. Here's the honest version:

New item creation requires a workaround: there's a locale ID requirement that needs a human step to resolve. Static page content in the Designer isn't accessible through the connector; that still requires opening Webflow directly. All visual and layout decisions remain entirely human. And most importantly, the editorial judgment that determines whether output actually sounds right for a specific client is something Claude cannot supply on its own.

The professionals who will get the most from this workflow are the ones with strong enough Webflow fundamentals to know exactly what to hand off, and strong enough editorial instincts to know when the output needs another pass.

What This Means for Organizations

For organizations running Webflow sites, the practical implication is that ongoing web management can look different now.

Keeping a site current has always been valuable: fresh content, consistent voice, SEO that gets tended to rather than set up once and forgotten. The reason it often doesn't happen is that the manual effort made it expensive relative to the return. A blog post here, a service description there, one item at a time.

What's changed is scale. Strategic web attention that used to require many hours of manual CMS work can now happen in a single focused session, guided by a professional who knows both the platform and the content strategy behind it.

That's not automation. It's a more capable version of the ongoing web partnership that good sites have always needed.

Getting Started

If you're a Webflow professional ready to explore this workflow, Webflow's own documentation is a solid starting point. Their connector announcement covers setup and includes a prompt library worth bookmarking.

If you're an organization wondering what this could mean for your Webflow site, I'd love to talk through what ongoing AI-assisted web management could look like for you specifically.

Reach out here, or keep reading on the MacPhee Design blog for more on working with Claude across real Webflow projects.

Susan MacPhee is the principal of MacPhee Design, a Webflow Premium Partner specializing in Webflow design, development, and CMS strategy. Greater Boston.