a product i build, not a client job
SiteHelm. A WordPress MCP server you can point at a client site.
Everyone connecting an AI agent to WordPress today is handing it either raw database access or a pile of REST credentials, then hoping. I did not want hope in that sentence, so I built the WordPress MCP server I would trust on a client site. It runs as a plugin, speaks the same protocol Claude and a growing list of editors use, and gives the agent 166 named operations across content, media, menus, Elementor, custom fields, SEO, forms, comments, users and settings. What it never gives the agent is PHP, SQL or a shell. Not at any price.
Five gates on every write.
None of them skippable.
The safety model is the product. An operation the agent calls does not simply run; it passes five gates, in order, and the caller cannot switch any of them off.
- 01
Preview
The write is planned as an exact diff before anything changes.
- 02
Capability
The WordPress user’s permission is re-checked inside every handler. The agent can never do what that user could not do by hand.
- 03
Snapshot
The prior state is captured before the write lands.
- 04
Verification
The result is read back and compared against what the preview promised. A mismatch is reported as a failure, not a success.
- 05
Rollback
Anything recorded can be rolled back from the admin console, in one click.
There is no permanent delete in the operation surface at all: trash is as far as an agent can go, and trash rolls back. The full model is written up atwpsitehelm.com/safety.
Free is the whole safety model.
Pro is the scale.
All 115 free operations, the preview gate, the capability checks, the snapshots, the verification, the rollback and every permission switch are free, permanently. The Pro add-on sells 51 operations for the work that spans a whole site or a whole shop: bulk edits, WooCommerce, deep SEO, Elementor Pro surfaces and a code module. Nothing that decides whether a write is safe is ever behind the paywall, because trust is the reason anyone considers paying at all.
Free against Pro, area by areaPricingThe full operation catalogue
Straight answers about the server.
What is a WordPress MCP server?
MCP, the Model Context Protocol, is the standard way an AI client asks an outside system to do something. A WordPress MCP server exposes your site as a set of named operations an agent can call, so instead of pasting code into the editor and hoping, the agent asks for the operation it wants and the site decides whether to allow it. SiteHelm is that server, running inside WordPress as a plugin rather than as a separate service holding your credentials.
Is it free?
Yes. The free plugin is GPL licensed and carries all 115 core operations plus the whole safety model: preview, capability checks, snapshots, verification and rollback. Nothing about safety sits behind a paywall. The Pro add-on adds 51 operations for SEO, WooCommerce, Elementor, plugin and theme management, and code.
Which AI clients can connect to it?
Any client that speaks MCP. In practice that means Claude Code, the Claude desktop app, and the growing set of editors and agents that have added MCP support. The server implements the 2025-06-18 revision of the protocol, so a client that follows the spec does not need anything SiteHelm specific to talk to it.
Can an agent break the site through it?
That is the whole question, and it is why the five gates exist. A write is previewed as a diff before it runs, checked against the WordPress capability the logged in user actually holds, snapshotted so the previous state is recoverable, verified after the fact against what was asked for, and reversible if the verification disagrees. An agent can still make a bad editorial decision. What it cannot easily do is make an irreversible one.
How is this different from your Search Console MCP server?
Different site, different job. The Search Console MCP server is read and report: it pulls performance data and index status out of Google so an agent can reason about what is happening. SiteHelm is write: it changes the WordPress site once you have decided what needs changing. I use both, usually in that order.
Why this page is on a portfolio site.
Because SiteHelm is the same work as the rest of this site, in product form. My day job is keeping WordPress sites healthy and indexable; this plugin is that judgment shipped as software, from someone who has spent years being the person clients call after a tool broke something. The counts above are not typed on this page: they regenerate from the plugin's own operation reference before every build, the same pipeline the product site uses, so this page cannot drift from what the plugin actually ships.