Comparison
WP MCP vs the other WordPress MCP tools.
A handful of tools now let an AI agent connect to WordPress or WooCommerce over the Model Context Protocol and make changes directly. The question worth asking before you install any of them is not "what can it do", it is "what happens the moment it gets something wrong". This page compares WP MCP against the field on exactly that question, as plainly as we can put it.
Last reviewed July 2026 · judge us on the same page
The field, briefly
Four ways to wire an agent into WordPress.
This project, the wpmcp plugin
WP MCP
A WordPress plugin using the official WordPress Abilities API. Every mutating tool routes through one safety engine that snapshots the target before it changes, so a single operation or a whole agent session can be restored with one click. Free and GPL-2.0.
Official adapter / connector approach
Automattic's WordPress MCP connector
An official, well-maintained way to expose WordPress content and actions to an MCP client, built on the same underlying WordPress Abilities API foundation WP MCP uses. It focuses on exposing the surface; it does not ship a snapshot-and-restore safety layer of its own around every write.
Independent MCP server
Royal MCP
An independent open-source WordPress MCP implementation. Useful as a reference for tool coverage, but it does not build a dedicated before-image snapshot and one-click rollback engine into its write path.
Local Node proxy
Respira
Runs as a separate local Node process that proxies MCP calls to WordPress, rather than living inside WordPress as a plugin. That extra moving part is its own source of risk: Respira's own changelog has documented a bug that applied changes to the wrong connected site.
We are not neutral here, obviously, this is our own comparison page. Where we are not certain of a competitor's current internals we say so rather than guess, and we welcome corrections: email info@fahdmurtaza.com if something here is out of date.
The undo and audit moat
Snapshot, restore, audit. Nobody else pairs them.
A snapshot taken automatically before every write, a one-click restore for a single change or an entire agent session, and a visible history of what an agent did and when. Not a marketing claim, a mechanism: in WP MCP, no tool that writes to the database can skip it, because every mutation is required to route through one orchestrator (Safe_Mutation::run()) that snapshots first, applies second, and can reverse the change on demand.
| Capability | WP MCP | Automattic connector | Royal MCP | Respira |
|---|---|---|---|---|
| Runs as | Single WordPress plugin | WordPress-side connector | MCP server | Separate local Node process |
| Snapshot before every write | Yes, enforced in code | Not built in | Not built in | Not built in |
| One-click restore, single change | Yes, rollback-operation | No equivalent | No equivalent | No equivalent |
| One-click restore, whole agent session | Yes, rollback-session | No equivalent | No equivalent | No equivalent |
| Operation history / audit trail | Yes, last 20 free, unlimited on Pro | Standard WP revisions only | Varies by deployment | Varies by deployment |
| Content and page edits undoable | Yes | WP post revisions | Depends on host setup | Depends on host setup |
| Media edits undoable | Yes (metadata; see note) | Not built in | Not built in | Not built in |
| User profile edits undoable | Yes | Not built in | Not built in | Not built in |
| WooCommerce product edits undoable | Yes, exact price and stock restore | No native WooCommerce layer | Not built in | Not built in |
| WooCommerce order status changes undoable | Yes, HPOS- and CPT-safe | No native WooCommerce layer | Not built in | Not built in |
| Navigation menu edits undoable | Yes | Not built in | Not built in | Not built in |
| SEO metadata edits undoable | Yes, Yoast SEO and Rank Math | Not built in | Not built in | Not built in |
| Elementor page building | Yes, deep editing on Pro: 44-widget catalog, structural suite | Not built in | Not built in | Not built in |
| Runs inside WordPress, no extra process | Yes | Yes | Depends on hosting choice | No, local Node proxy required |
| License | GPL-2.0-or-later, free | GPL-2.0-or-later, free | Open source, check project | MIT wrapper, check project |
"Not built in" means the tool has no dedicated snapshot-and-restore mechanism for that domain, not that the tool is bad at what it does. Media restores cover metadata; disk bytes are handled by the separate file-backup path.