Enforced in code, not by convention
No tool that writes to the database can bypass the safety wrapper. It is a structural guarantee, not a guideline the code happens to follow.
WP MCP lets an AI agent build and run a WordPress site, and quietly saves a copy of everything before it touches it. If the agent ever gets something wrong, one click puts the site back exactly as it was. This page explains what it is, why it works this way, and who is behind it.
WP MCP is a WordPress plugin, built on the official WordPress Abilities API. Once installed, it turns a site into something an AI agent can safely operate: the agent can create and edit pages and products, adjust settings, manage media, moderate comments, update WooCommerce orders, and more. It speaks the Model Context Protocol (MCP), so it works with Claude, Cursor, and any other compatible AI client through a standard connection secured by a WordPress application password.
The part that makes WP MCP different is not what the agent can do. It is what happens the instant before it does it. Every change that touches the database is routed through one safety engine that saves a snapshot of the affected object first. That snapshot is what a one-click restore reads from, whether you undo a single change or roll back a whole agent session.
The core promise
WP MCP assumes the agent will get something wrong eventually, and makes sure that when it does, the fix is a button, not a backup restore and a stressful afternoon.
Most AI-for-WordPress tools focus on the building experience and ask you to trust the model. Trust is not a safety net. AI is good, not perfect, and one bad change on a live site is a broken client homepage or a lost sale. WP MCP treats recoverability as the headline feature, not an afterthought, and builds it into the write path itself.
No tool that writes to the database can bypass the safety wrapper. It is a structural guarantee, not a guideline the code happens to follow.
Snapshots capture the real post row, meta, terms, and comments, so a restore works the same no matter which page builder or theme created the page.
One plugin, no separate service and no third party holding a copy of your site. Your data stays self-hosted, on your server.
The save, restore, and audit engine is GPL-2.0 and free forever. The safety net is never the upsell.
WP MCP is the open-source plugin wpmcp and now registers well over eighty abilities across the whole site: content and pages, media, site settings, users and comments, WooCommerce products and orders and sales reports, navigation menus, plugins and themes, a read-mostly database and filesystem surface, and read-only performance and security scanners. Content, product, order-status, comment, menu, and settings changes are snapshotted and one-click undoable. A few deliberately risky paths, raw database writes and package or file deletions, are off by default and honestly report that they are not covered by the undo guarantee, rather than pretending everything is reversible.
WP MCP is an early release. The safety engine (snapshot, apply, verify, rollback) and the first broad set of read and write tools are shipped and covered by tests. Some capabilities described on the roadmap, such as Elementor deep editing, dry-run change previews, and an unlimited-history Pro tier, are planned and not all shipped yet. Where the documentation describes a planned feature, it says so. We would rather under-promise here than surprise you on a production site.
Ready to try it? See how the undo works, read the documentation, or compare WP MCP with the other WordPress MCP tools on the comparison page.