Get the plugin

About

An undo button for the age of AI site-building.

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.

Free and open · GPL-2.0-or-later · built on the WordPress Abilities API

What WP MCP is

A plugin that makes your site safely operable by an agent.

WP MCP is a WordPress plugin, built on the officialWordPress 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.

Why it works this way

Trust is not a safety net.

Most AI-for-WordPress tools focus on the building experience and ask you to trust the model. 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.

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.

Works at the data layer

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.

Runs inside your WordPress

One plugin, no separate service and no third party holding a copy of your site. Your data stays self-hosted, on your server.

Free where it matters

The save, restore, and audit engine is GPL-2.0 and free forever. The safety net is never the upsell.

Scope, stated plainly

What it covers today.

WP MCP is the open-source plugin wpmcp and registers188 abilities (163 free, 25 Pro) across the whole site: content and pages, media and stock imports, site settings, users and comments, WooCommerce products, orders and sales reports, navigation menus, plugins and themes, SEO metadata through Yoast SEO and Rank Math, deep Elementor editing on Pro, 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, guarded code execution, 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. Where the documentation describes a planned feature, it says so. We would rather under-promise here than surprise you on a production site.

Who it is for: developers and agencies letting an agent maintain sites, including client sites; MCP client users connecting Claude Code, Claude Desktop, or Cursor to a WordPress install; WooCommerce store owners who want AI help without gambling the live store; and anyone nervous about giving an AI write access to production who wants an undo button that actually works.

Who builds it

Built by a WordPress plugin developer, in the open.

WP MCP is built by Fahad Murtaza, a WordPress plugin developer who has spent years shipping tools for the WordPress and WooCommerce ecosystem. The project grew out of a simple observation: AI agents are getting write access to production sites, and nobody was shipping the undo button.

Development happens in the open onGitHub, with honest release notes, including which paths are verified in CI and which are production-only.

Release notes, straight to your inbox.

One email per release, what shipped, what's verified, what's production-only. No drip campaigns. Unsubscribe in one click.