You want to point Claude at your Webflow CMS and say tighten every blog excerpt, fix the SEO titles, swap the old product name across all 400 items. What stops you is the live site. Webflow has no undo, and most ways of wiring AI to a CMS write straight to it, so one confident pass is published before you can read it.
Scratch changes where the edit happens. Claude does 99% of the work, reading and rewriting every item in your collections as files on your laptop. The last 1%, deciding what actually publishes, stays with you. Nothing reaches the live site until you have seen the change as a diff and approved it.
How it works
- Scratch pulls your collections into files. Every CMS item, page, and asset comes down to a folder on your laptop, one file per item. The Designer layout never moves.
- Claude rewrites the fields you point it at. Open the folder in the Claude desktop app. Try a prompt on one item in Chat, then let Cowork or Code run it across the whole collection. Rewrite every excerpt to one sentence and fix the title case. Claude edits the files, never 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 you do not approve never leaves your laptop.
What people use it for
Most people arrive with a job they have been putting off, because doing it by hand means opening every CMS item one at a time.
- Tighten every blog excerpt to one sentence and fix inconsistent title case.
- Write the missing SEO title and meta description on every case study, each inside Webflow's limits.
- Push a rebrand through a collection: swap the old product name in body copy, headings, and SEO fields in one pass.
- Add alt text across an image-heavy collection.
- Localize a collection into a second language, where Webflow exposes locales.
Pull a handful of items to feel the loop, then point Claude at the whole collection.
Why not an MCP server?
A Webflow MCP server hands Claude a direct line to your live CMS. The publish button is wired straight in, so one confident rewrite ships 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. The publish step is pulled out and handed to you. Claude can change anything; only you can ship it. On a live site with no undo, that is the difference that matters.
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 are never exposed for editing. Validators check length caps, slug uniqueness, and any field you flag as never-touch, so a rewrite that blows past an SEO limit or drifts toward a binding is flagged right on the diff. Ecommerce collections are out of scope. For the full field list, see Scratch for Webflow.
Questions people ask
Is this an MCP server or a Webflow app?
No. An MCP or app 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 content fields. Layout, components, bindings, and reference targets are never exposed for editing, and validators flag a broken slug or an overlong field right on the diff before you approve it.
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.
Why not just bulk-edit with a CSV or a script?
A CSV round-trip and a custom script both write straight to the live CMS with no diff and no per-item approval, and a find-and-replace only does exactly what you spelled out. Scratch puts an agent on the edit, so it handles the messy cases a rule cannot, and holds every change as a word-level diff you approve before anything ships.
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. Cowork and Code are built for collection-scale jobs.
Do I need to be technical?
No. Install Scratch, connect Webflow, point Claude at the folder, and approve the diffs. Validators are optional, for when you run the same job often enough to want guardrails.
See it on your own collections
The fastest way to trust it is to watch it run on your content. Book a 30-minute demo on your Webflow CMS →, or try Scratch free and run the first pass yourself.