The right level of automation for an AI agent is 99%. Claude can read and rewrite every item in your Webflow CMS. The last 1%, deciding what actually publishes to the live site, stays with you. Webflow has no undo, so that review step is the whole point.
How it works
- Scratch pulls your collections into files. Every CMS item, page, and asset comes down to a folder on your laptop. The Designer layout never moves.
- Claude rewrites the prose fields. Tell it what you want across a collection. Tighten every blog excerpt to one sentence and fix the title case. Claude edits the files, not the live site.
- You review every diff and publish. Scratch shows each change next to the original, word by word. Approve what ships, and Scratch publishes only those items back through the Webflow CMS API.
What Claude edits in Webflow
- CMS collection items: rich-text, plain-text, slug, and custom fields
- Page metadata: title, slug, SEO and Open Graph
- Asset alt text
- Multi-locale content, where Webflow exposes it
Designer layout, components, bindings, and reference targets stay untouched. Ecommerce collections are out of scope. For the full picture, see Scratch for Webflow.
Why not an MCP server?
A Webflow MCP server hands Claude a direct line to your live CMS. One bad rewrite publishes across the whole collection, and Webflow gives you nothing to undo it with. Scratch gives Claude the same full read and write access, but against a local copy. Every change waits as a diff until you approve it. What you do not approve never leaves your laptop.
Questions people ask
Is this an MCP server or a Webflow app?
No. An MCP gives Claude the publish button straight to your CMS. Scratch does not. Claude gets the same access, but publishing is a separate step you approve, one item at a time.
Will Claude break my Designer layout?
No. Claude only touches the content fields. Layout, components, bindings, and reference targets are never exposed for editing.
Can I undo a change after it ships?
Yes. Every published item is reversible from Scratch, per row, even though Webflow itself has no undo. The original sits next to the rewrite until you decide which one stays.
Can it handle a whole collection at once?
Yes, that is the use case. Pull a few items to feel the flow, then pull the whole collection.
Do I need to be technical?
No. Install Scratch, connect Webflow, point Claude at the folder, and approve the diffs.