Launch offer
20% off every Pro tier — and every renewal — for a limited time. Use the code at checkout:
Questions
25 answers, including the ones where the honest answer is no. Where another tool is a better fit for what you are doing, the answer says so.
Nothing here is a number typed into a marketing page — the counts and prices come from the same files the catalogue and the checkout links are built from.
It is a WordPress plugin that exposes the site to an AI agent over MCP, the Model Context Protocol. The agent gets 166 named operations — 115 free and 51 in the paid add-on — covering content, media, menus, Elementor, custom fields, SEO, comments, users and site settings. It does not get PHP, SQL or a shell.
Anything that speaks MCP. That currently includes Claude Desktop, Claude Code, and a growing number of editors and agent frameworks. The connection is either a WordPress Application Password or an app that signs in to the site itself and is approved from your own dashboard, so nothing about your site is stored anywhere else.
No. SiteHelm contains no model, sends nothing to any AI service, and writes no content of its own. It is the safe hands the agent you already use operates the site with.
The plugin is only useful with one. There is a WordPress admin console for reviewing history, rolling changes back and controlling permissions, but the operations themselves are called by an agent.
Five gates on every write, and none of them can be skipped by the caller. The write is previewed as an exact diff; the WordPress user’s capability is checked; the prior state is snapshotted; the write is read back and compared against what the preview promised; and anything recorded can be rolled back from the admin.
No, and not at any price. There is no eval, no snippet store, no theme-file editor, no query passthrough and no WP-CLI passthrough. These are excluded from the product rather than held back from a tier.
No. There is no permanent delete in the operation surface. A trash operation moves an item to the bin and declares that rollback is required.
One switch in the admin pauses every write on the site immediately. Individual operations and whole modules can also be switched off, and a connected application can be revoked without touching the others. None of these controls is reachable by an agent.
No. Every operation re-checks the WordPress capability of the authenticated user in the handler itself, and refuses if the user could not have made the change by hand. The permission switches live in wp-admin and are not exposed over MCP.
No — try it on staging, with reads only, and watch a preview or two. That is true of any tool that can write to a live site, and it is the advice we would give about ours.
Nothing that decides whether a write is safe. All 115 free operations, the preview gate, the capability checks, the snapshots, the verification, the rollback, the activity log and every switch are free, permanently. Pro adds 51 operations for surfaces the free plugin does not reach — a shop, a plugin list, a site-wide settings screen. Batch size is not one of them: changing fifty posts under a single preview is free.
No. Pro adds operations; it never takes one away. The plugin is open source, so this is checkable rather than promised.
From $24.99 a year for a single site, with 5-site and unlimited tiers, a monthly option on unlimited, and a pay-once lifetime price on each yearly tier. Every tier gets every Pro operation — nothing is held back for the expensive one.
No. Sales are final. The free plugin is the trial — every read, every core write and the whole safety layer, on as many sites as you like — so you know exactly what Pro adds before you pay for it. You can cancel a renewal at any time and the term you paid for runs to its end.
Yes. Deactivate the site from your account and activate another. The tier is the number of sites active at once, not the number you are allowed to try.
No. The free plugin has no trial clock, no call quota and no seat count, and it keeps working whether or not you ever buy anything. A lapsed Pro licence stops the Pro operations; nothing free stops.
WordPress 6.6 or newer and PHP 8.1 or newer. It is installed like any other plugin: upload the zip under Plugins, Add New, Upload.
It does no work on a front-end page view. The operations run only when an agent calls one, over an authenticated endpoint.
The plugin makes no outbound call except the update check against its GitHub releases, the licence check for Pro, and the media-import operation when you explicitly ask it to fetch a URL — and that fetch is guarded against reaching your internal network. Your content is never sent anywhere.
The refusal names which of thirteen codes applies and what to do about it, and says how far the run got. If a write landed but the read-back disagreed with the preview, that is reported as a verification failure rather than a success.
Yes, where the plugin is active and at or above its supported version. If it is missing the operation refuses with a message naming what to activate, rather than failing obscurely. SEO covers seven providers in a defined precedence order.
The free plugin is, including its tests and its operation reference. The Pro add-on is not. You can read exactly where the licence gate is and what it gates.
Requests are public and votable, and the votes are read. Voting influences priority; it does not guarantee that something is built, and nothing carries a promised date.
Yes, and meaningful contributions are rewarded with free Pro access. Rewards are for verified, approved work — a maintainer reads it and decides — so no amount of GitHub activity earns anything automatically. There is no beta or early-access programme.
No. It is an independent plugin and is not endorsed by the WordPress project or by Automattic.
If you got this far without the answer you needed, the question is worth asking — and it is worth adding to this page afterwards.
SiteHelm