Hermes is a CLI agent that remembers. Every session it can carry what it learned forward, building reusable skills from the work it completes. Point it at your Webflow CMS for a content overhaul, and after that first pass it has a skill for your catalog structure, your field names, your patterns. The second pass starts from that skill and moves faster. The problem is the live site. Webflow has no undo, and there is nothing in a standard Hermes setup to stop a confident rewrite from shipping before you have read it.
Scratch adds that stop. Your CMS collections come down to a folder on your laptop, one file per item. Hermes does 99% of the work, rewriting every item against those files the same way it would against a local project. The last 1%, what actually reaches the live site, stays with you. Nothing publishes until you have seen the diff and approved it. The Designer never moves.
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, components, and bindings never move.
- Hermes edits the fields you point it at. Open the Scratch folder in Hermes and describe the job. Hermes can search across files, run comparisons, and apply changes at whatever scale you need. On the first pass it builds a skill for your catalog. On every pass after that, it starts from what it already knows. It edits the files, never the live CMS.
- You review every diff and publish. Scratch shows each change beside the original, word by word. Approve what ships, and Scratch sends only those items back through the Webflow CMS API. What you do not approve stays local.
What people use it for
The jobs that pile up because the Webflow editor opens one item at a time:
- Rewrite every blog excerpt to a single tight sentence, fix inconsistent title case across a whole collection.
- Backfill the SEO title and meta description on every case study that shipped without them.
- Carry a rebrand through a collection: swap the old product name in body copy, headings, and SEO fields in one pass.
- Let Hermes score items for internal linking gaps and draft the anchor text. Cross-reference a sibling folder if you have one.
- Localize a collection into a second language, where Webflow exposes locales.
Run it on a handful of items to settle the prompt and let Hermes build its skill. Then point it at the full collection.
Why not an MCP server?
A Webflow MCP server wires Hermes straight to your live CMS. The publish step is bundled into the tool call, so one confident pass ships across the whole collection. Webflow gives you nothing to roll it back with. Hermes's memory makes it fast, and that speed is exactly what makes the live-write risk worse, not better.
Scratch separates the two things. Hermes gets the same full read and write access it would have through an MCP, but against a local copy. Publishing is pulled out of the agent loop and handed to you as a separate step. Hermes can change anything; only you can ship it. On a live site with no undo, that is the architecture that lets you actually trust the agent.
What Hermes 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 mark off-limits, so a rewrite cannot overrun an SEO limit or quietly break a binding. Ecommerce collections are out of scope. The full field list is on Scratch for Webflow.
Questions people ask
Is this an MCP server or a native integration?
Neither. An MCP server wires Hermes to your live CMS with the publish step bundled in. Scratch keeps the publish step with you. Hermes gets the same access to your content, but nothing ships until you approve it, one item at a time.
Will Hermes touch my Designer layout?
No. Hermes 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 running past a length cap.
Webflow has no undo. Am I stuck if a rewrite is wrong?
No. Scratch keeps the original beside every rewrite, and you can roll back any published item per row, even though Webflow itself cannot. You decide which version stays.
What does Hermes actually remember, and does it help?
Hermes can persist a skill from the first Scratch session: your collection structure, your field names, the kinds of edits your content needs. On subsequent runs it starts from that skill rather than re-reading everything cold. Larger catalogs and repeated jobs compound that benefit most.
Do I need to be a developer to set this up?
You need to be comfortable running Hermes from a terminal. If you already run it, setup is the same as any local project. If you prefer a desktop surface for the same Scratch loop, the Claude desktop app works identically.
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 run the first pass yourself.