Get the plugin
WP MCP/Blog/Post

· v1.0.0

WP MCP 1.0: the first production release

release

WP MCP 1.0 is out. It is the first version we call production grade: the release where the safety engine, the tool surface and the integrations are stable enough that we stand behind them on a live site, not only on staging.

Nothing about the product changes shape at 1.0. It is the same plugin that 0.9.1 was, with one more round of fixes, and it keeps the same promise: an AI agent can work on your WordPress site, and every change it makes can be seen and undone.

What 1.0 means

  • The safety model is the contract. Snapshot, apply, verify and rollback are not a feature that some tools have. Every supported write goes through them, and the writes that cannot be undone say so before they run.
  • Honest limits stay in writing. What cannot be undone, which clients are tested most and which integration paths are verified on a live install instead of in CI are listed in the docs, and a release note says so when that list changes.

What is covered

  • 407 abilities (MCP tools): 274 in the free plugin and 133 in Pro. The count comes from the plugin’s ability manifest, which the test suite checks on every run, so it cannot drift from what the plugin registers. Tools for an optional plugin register only where that plugin is active, and list-tool-catalog lists exactly what your site has.
  • More than 100 integrations across page builders, WooCommerce, SEO, forms, multilingual, LMS and membership, CRM, email and SMTP, caching, security, backups and themes. Each one has its own page on the integrations hub, with what it reads, what it writes and whether it needs Pro.
  • Every MCP client that speaks the protocol. Claude Code and Claude Desktop are the most tested and work on a default install with an Application Password. Clients that sign in only with OAuth, ChatGPT among them, need OAuth switched on first. The client guide has the current state for each one.

The safety model

  • A snapshot before every write. Before a supported write, WP MCP stores the before-image of what it is about to change: post content and meta, options, orders, builder layouts, plugin table rows. If a post-write check fails, for example block markup that no longer parses, the change rolls back on its own.
  • Undo one step or a whole run. rollback-operation restores one change, rollback-session unwinds everything an agent did in one session, and the History screen in wp-admin has a Restore button on every row. Free keeps the last 20 operations by default (a filter raises it), and Pro keeps unlimited history while the licence is active.
  • Confirmations for what cannot be undone. Destructive and non-reversible operations, such as permanent deletes, a WooCommerce refund or running a queued job now, are off until the site turns them on, run only when the agent’s own call carries confirm: true, and answer recoverable: false instead of implying an undo that does not exist.
  • Masking before the model sees it. List reads mask personal data on the server (j***@example.com) and say masked: true, while a single-record read still returns the full value to someone allowed to see it. Option reads pass through one registry of secret options, so a stored API key is not handed to the model in plain text.
  • Narrowing permissions only. Scoped identities give each agent only the capabilities it needs, and every governance layer can narrow access, never widen it. OAuth ships off and, when on, lets you approve a client with read-only access.

The safety model covers each of these in detail, including the cases that are not covered.

What changes in 1.0

These are the changes you will notice after updating:

  • Irreversible actions need confirm: true in the call itself. A client’s own confirmation answer no longer counts for an action that cannot be undone, because a client set to skip permission prompts answers that question by itself. This covers irreversible integration operations, the Wordfence IP block, unblock and scan issue ignore operations, deleting menus, plugins and themes, plugin and theme updates, content imports and REST writes.
  • Writes refuse arguments they do not understand. An integration write with a misspelled or unknown argument is refused with invalid_args, naming the unknown and the accepted keys, instead of quietly falling back to a default and writing anyway.
  • Media deletes refuse when files cannot be backed up. A permanent delete-media and resize-media stop and name the files when a backup copy fails. Passing allow_unrecoverable_files: true goes ahead, and the result then says files_recoverable: false.
  • Elementor writes respect the WordPress editor. A page that has WordPress editor content and was never built in Elementor is refused, because Elementor would hide that content. A blank page is marked as an Elementor page, so the change shows on the site.
  • Code layouts stay behind their gate. Theme layouts that run code, in GeneratePress Premium, Astra Pro and Kadence Pro, cannot be published through the generic post tools, and the layout tools publish them only when the site allows that code.
  • A new Opt-in operations screen. WP MCP > Opt-in operations switches on the operation groups that are off by default, which could only be enabled in code before. Every toggle starts off and every change is recorded in the audit log.

Fixes in this release

  • Refusals name what is missing: the capability, the plugin to install or activate, or that Application Passwords are switched off.
  • Large site backups are built in resumable steps on hosts with a PHP time limit, and a stopped restore no longer blocks the recovery restore it recommends.
  • An undo saves the restored builder layout on the revision it creates, so restoring that revision no longer brings the undone change back.
  • More masking in list reads: WP Mail SMTP and UpdraftPlus logins in option reads, every member a BuddyPress activity names, WooCommerce refund reasons and usernames in activity log messages.
  • Avada pages that also carry the WPBakery flag are read as Avada, and Elementor add-on widget summaries such as JetElements are about four times smaller.
  • SureForms and Fluent Forms entry lists return the right rows, and entry delete confirmations say the delete is not an erasure.
  • WooCommerce list-orders no longer fails on refunds, and the sales report no longer counts refunds as orders.
  • Oxygen Components and Elementor templates follow the publish permission.
  • Action Scheduler, Code Snippets, BetterDocs and Divi fixes, plus bbPress topic tags, Kadence Pro element expiry settings and attachment lists for Fluent Support and Awesome Support tickets.
  • The Abilities screen in wp-admin has collapsible domains, search and filters, and WP MCP has its own menu icon.

Upgrading

  • WP MCP 1.0 needs WordPress 6.9 or later and PHP 8.1 or later, the same as 0.9.1.
  • Defaults do not change on upgrade: OAuth stays off until you switch it on, and every opt-in write stays off until the site turns it on.
  • After updating, run list-tool-catalog from your MCP client to see the tools your site now has.
  • There is no database migration: the update replaces the plugin files, and new settings such as the Opt-in operations toggles start off.
  • Updates arrive on your WordPress updates screen through Freemius once you opt in on the plugin’s activation screen, for Pro as well; otherwise download the new zip from the GitHub release and reinstall it.

Download it from the GitHub release, or see this release on the changelog alongside every earlier one.