You already point Cursor at a repo and let it rewrite files, reading the diff before you accept. Your Webflow CMS is the one place you cannot do that. The bulk pass you keep putting off, retitle every case study, fix the SEO descriptions, swap a product name across 400 items, would have to run against the live site, and Webflow has no undo.
Scratch turns your collections into a folder Cursor opens like any other. Cursor does 99% of the work, rewriting every item on your laptop. The last 1%, what actually publishes, stays a button only you press. Nothing reaches the live site until you have read the diff and approved it.
How it works
- Scratch pulls your collections into files. Every CMS item, page, and asset lands in a folder on your laptop, one file each. The Designer layout never moves.
- Cursor edits the items. Open the folder in Cursor. Cmd+K one item to get the prompt right, then turn on Agent mode and let it walk the collection. Rewrite every excerpt to one sentence and fix the title case. Cursor touches the files, never the live site.
- You review every diff and publish. Scratch lays each change next to the original, word by word. Approve what ships, and Scratch sends only those items back through the Webflow CMS API.
What people use it for
The jobs that pile up because the Webflow editor makes you open one item at a time:
- Collapse every blog excerpt to a single clean sentence and fix the title case.
- Backfill the SEO title and meta description on a collection that shipped without them.
- Carry a rename through a whole collection: body copy, headings, and SEO fields in one sweep.
- Write alt text across an image-heavy gallery or case-study set.
- Localize a collection into a second language, where Webflow exposes locales.
Cmd+K one item to feel the loop, then let Agent mode take the rest.
Why not an MCP server?
A Webflow MCP server wires Cursor straight to your live CMS, publish button and all. One confident Agent-mode pass ships across the whole collection, and Webflow hands you nothing to roll it back with.
Scratch gives Cursor the same full read and write access, but against a local copy. The publish step is lifted out and handed to you. Cursor can change anything; only you can ship it. On a live site with no undo, that gap is the whole point.
What Cursor 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
The Designer layout, components, bindings, and reference targets are never exposed for editing. Validators check length caps, slug uniqueness, and any field you mark off-limits, so a rewrite cannot overrun an SEO limit or quietly break a binding. Ecommerce collections are out of scope. The full list lives on Scratch for Webflow.
Questions people ask
Is this an MCP server or a Cursor extension?
Neither. An MCP or an extension hands Cursor the publish button. Scratch keeps it. Cursor gets the same access, and publishing is a separate step you approve, one item at a time.
Will it touch my Designer layout?
No. Cursor only sees content fields. Layout, components, bindings, and reference targets are never pulled into the folder, and validators stop a rewrite from breaking a slug or blowing a length cap.
Webflow has no undo. Am I stuck if a change is wrong?
No. Scratch keeps the original beside the rewrite, so every published item rolls back per row, even though Webflow itself cannot. You decide which version stays.
How is this different from a CSV round-trip or a script?
A CSV re-import and a hand-written script both write straight to the live CMS with no diff and no per-item approval, and a find-and-replace does only what you spelled out. Cursor brings judgment to the messy items a rule misses, and Scratch still holds every change for review before it ships.
Can it sweep a whole collection at once?
Yes, that is the point of Agent mode. Cmd+K one item to settle the prompt, then let Agent mode walk the whole collection.
Do I need to be technical?
If you run Cursor already, you are set. If you would rather not work in an editor at all, the Claude desktop app runs the same Scratch loop with a more familiar surface.
See it on your own collection
The fastest way to trust it is to watch it run on your content. See it run on your Webflow CMS →, or download Scratch free and take the first pass yourself.