An archive cleanup is never one instruction. It is a sequence: find the posts that need work, decide what each one needs, make the edits, report what changed. That is the shape of job Antigravity was built around. Google's agent-first IDE runs agents against a workspace of files, planning in the open, working step by step while you watch. What it needs is your archive as a workspace, and a reason to believe none of this touches the live site.
Scratch provides both. Your posts, pages, and custom types come down as a folder on your machine, one file each, and the Antigravity agent does 99% of the work there: the audit, the fixes, the whole visible sequence. The last 1% is yours. Every change waits in Scratch as a word-level diff, you approve post by post, and only the approved ones write back over the REST API. Your readers never see a draft.
How it works
- Scratch pulls your content into files. Posts, pages, and any custom post types land in a folder on your machine, auto-discovered, one file each.
- Antigravity's agent works the folder. Open the Scratch folder as a workspace and describe the whole job. Audit the archive for posts missing meta descriptions, list them, then write one for each, under 158 characters. The agent plans, audits, and edits in plain sight, file by file. It edits the files, never the live site.
- You review every diff and publish. Scratch shows each change beside the original, word by word. Approve what ships, and Scratch writes only those posts back over the REST API.
What people use it for
The archive work that is really several jobs in a trench coat:
- Audit for missing meta descriptions, then backfill them, each under the cap.
- Find the posts that still name an old product, price, or policy, then refresh them.
- Fix inconsistent title case and formatting across the whole archive.
- Write alt text across the media library, with the findings listed before the fixes.
- Tidy excerpts, categories, and tags so archives and feeds read cleanly.
Ask for the audit first. The edit pass is easier to approve once you have read what the agent found.
Why not an MCP server?
A WordPress MCP server wires the agent straight to your live database. A multi-step job makes that worse, not better: each step writes to production as it happens, so by the time you disagree with step two, steps one and two are already live.
Scratch lets the whole sequence run against a local copy instead. The agent audits, fixes, and iterates freely in the workspace, and none of it touches WordPress until you approve the diffs, post by post. The sequence is the agent's. The site is yours.
What Antigravity edits in WordPress
- Post and page bodies, with block content preserved
- Titles, slugs, excerpts, and publication status
- Custom post types and taxonomies, auto-discovered
- Advanced Custom Fields and image alt text across the media library
Templates and template parts are excluded, and post meta is hidden by default, so plugin-owned SEO fields stay out of reach unless you expose them. Validators check length caps and any rule you set, and flag failures right next to the diff. For the full picture, see Scratch for WordPress.
Questions people ask
Is this a WordPress MCP server or a plugin?
Neither. Both of those write to your live database from inside the agent loop. With Scratch, the agent edits a local copy, and publishing is a separate step you approve, one post at a time.
Can it audit before it edits?
Yes, and that is the right way to run it. Ask the agent for findings first: which posts, what problems, what it proposes. The plan and the findings sit in the editor where you can read them, and the edit pass only starts when you say so. Scratch then holds every edit for a second read as a diff.
Will it overwrite the SEO fields my plugin owns?
No. Post meta is hidden by default, so fields managed by your SEO plugin are not in scope unless you explicitly expose them. Templates and template parts are excluded entirely.
Can I roll back a post after it publishes?
Yes. Scratch keeps the original beside the rewrite after publishing, per row. You decide which version stays live.
What is Antigravity?
Google's agent-first IDE: an editor built around agents that act on a workspace of files, with plans and progress visible as the agent works. You sign in with your own Google account. Scratch holds no Antigravity credentials and runs no model.
Do I need to be a developer?
It helps to be comfortable in an editor, but the loop is read and click: read the plan, read the diffs, approve. If an IDE is not your surface, the Claude desktop app runs the same Scratch loop as a plain desktop app.
See it on your own archive
The fastest way to trust it is to watch it run on your posts. Book a 30-minute demo on your WordPress site →, or try Scratch free and take the first pass yourself.