Press slash to focus this field, or Escape to return home.

How do you use Claude Code and MCP?

Tools

Claude Code drives Webflow from the terminal through MCP: the structural work that used to be several thousand clicks in the Designer.

MCP exposes Webflow as tools an agent can call: element trees, CMS collections and fields, component props and variants, page metadata, schema, assets. That makes the structural half of a build scriptable, repeatable and reviewable.

What it changes in practice is scale. Modelling a CMS becomes a conversation. Porting a component library between projects is one run. An audit covers every page. Judgment stays with me: spacing, colour, type and states are visual decisions, still made by eye in the Designer.

The rules that keep it safe are written down and version-controlled, because an agent holding write access to hundreds of client sites is exactly as careful as its instructions are.

RoleStructure, CMS, audits
RunsTerminal, locally
InterfaceWebflow MCP 2.0.1
Publish rightsNone, hook-gated

The rules I hold

Two hands, and I always know which one I am using

Structure, CMS and audits go through MCP. Spacing, colour, typography and states are visual judgment and happen in the Designer. Routing a visual decision through an API call is how builds end up technically correct and obviously wrong.

Third-party components get pasted in

Webflow's own copy-paste is lossless: 24 styles with full properties, every data attribute and semantic tag intact. Reconstructing the same component through the API dropped a class in the same session.

One call, one thing

Large batched writes time out and leave half-applied state behind, which is worse than failing outright.

Byte-exact readback is the acceptance test

I read the change back and compare it against what I sent.

A failed call escalates to the browser

An API call that errors or returns empty leaves the question open. The second hand goes and looks.

Publishing waits for my explicit go

A pre-flight hook enforces it, so the block sits in code and holds on every run.

Every rule it follows is a file in git

Dated, attributed to the observation that produced it, and reviewable. An undocumented rule is one nobody can correct.

← All six tools