WordPress 7.2 for AI: what changes for site owners

What does WordPress 7.2 change for AI?

WordPress 7.2 is the first release where core itself starts describing what an AI agent may do on a site. Three pieces are moving together: the Abilities API that shipped in 6.9 gains its first core-registered content abilities, a Secrets API for storing provider keys is heading into core, and the official MCP Adapter — the bridge that exposes those abilities to AI apps — is now a one-click install from the WordPress.org directory. None of the three is a finished AI feature on its own, and the release is still in beta, so this guide separates what is confirmed from what is planned, and says plainly what still needs a plugin.

The schedule, from the official 7.2 release page (opens in new tab): Beta 1 on 20 October 2026, further betas weekly through 10 November, release candidates from 17 November, and the final release on 8 December 2026. Features that are not ready by Beta 1 normally slip to a later release rather than shipping half-done, so treat anything below marked "planned" as exactly that until Beta 1 lands.

What are the core content abilities?

An ability is a named, described, permission-checked function that a plugin or core registers so that software — an AI agent included — can discover and call it. The Core AI team's plan for 7.2 is four content abilities split CRUD-style: core/content-query, core/content-create, core/content-update and core/content-delete, each annotated so a client can tell a read from a destructive write before it runs. The split is deliberate: a query can be marked read-only and a delete marked destructive, which lets an MCP client ask for confirmation on the right calls.

The pattern is already testable. The canonical AI plugin (opens in new tab) version 1.4.0 (5 October 2026) renamed its core/read-content ability to core/content-query, keeping the old name as a deprecated alias, and lists the create, update and delete abilities as its next work; the team said in August that the "current goal is for this abilities pattern to become part of WordPress Core in 7.2" (AI team summary, 20 August (opens in new tab)). Whether the four land in core at Beta 1 or stay in the AI plugin a little longer is the thing to watch on 20 October.

What they cover is posts, pages and other content types. What they do not cover is everything else a site owner asks an agent to do: WooCommerce products and orders, media, plugins and themes, users, settings, the database, caches, security scans, and any form of undo.

What is the Secrets API?

The Secrets API is a managed store for API keys and other credentials that plugins would otherwise keep as plain text in the options table. The Core AI team aligned on moving it into WordPress 7.2 (opens in new tab) after it had been available in the AI plugin, so that provider keys for OpenAI, Anthropic, Google and the like are stored and read through one audited path. It mostly matters to the AI plugin and to developers who build on the PHP AI Client.

For an MCP connection it changes little. MCP clients authenticate to your site with an OAuth connector or an API key, not with a provider key stored in WordPress, so the Secrets API neither replaces nor affects how Claude, ChatGPT or Cursor sign in. It is good hygiene for the keys that flow the other way — your site calling an AI model — and Cowboy MCP, which stores no provider keys at all, is unaffected by it.

What does the MCP Adapter on WordPress.org mean?

The adapter is the official bridge from abilities to the Model Context Protocol: it reads whatever abilities a site has registered and marked public, and serves them to AI apps as MCP tools from an endpoint on the site. Version 0.7.0 joined the WordPress.org plugin directory (opens in new tab) on 2 October 2026 under the WordPress.org author account, so it now installs like any plugin, updates itself, and can be declared as a dependency instead of being bundled. It requires WordPress 6.9 and adds support for the MCP specification's 2026-07-28 revision while keeping older clients connecting (announcement, 7 October (opens in new tab)).

Two things to keep straight. The adapter's own listing says it "does not provide any AI features itself": with no abilities registered there is nothing to call, so on a plain 7.1 site today it exposes the three discovery meta-tools and whatever other plugins have registered. And the project still describes itself as experimental, with a stable 1.0 as the goal. The AI team has also drafted a way for the AI plugin to switch MCP on with one toggle that installs the adapter; as of 13 October that is a draft, not a shipped setting (AI team summary, 2 September (opens in new tab)).

For a fuller side-by-side, including the Node.js proxy question and authentication, see Cowboy MCP vs the WordPress MCP Adapter.

What changes for a site owner in practice?

If you run a site and want an AI app to help run it, 7.2 makes the plumbing official without making the job done. After 7.2, a stock WordPress site with the adapter installed will let an AI app query, create, update and delete content through core-blessed abilities — and that is the extent of it, until plugins register abilities for everything else. Three consequences follow.

• The framework is the adapter; the server is still a plugin. The adapter turns registered abilities into tools. Something has to register the abilities — core for content, and plugins for WooCommerce, media, maintenance, diagnostics and the rest. A site that wants an agent to update plugins, read the error log, put a collection on sale or run a Wordfence scan still needs a plugin that provides those tools.
• Safety is not in the pipe. Confirmation before destructive calls, previews, undo and logging are left to the abilities and the client. The CRUD split helps a client ask before a delete; it does not give the site a way back after one. If an agent will touch a live site, the undo and checkpoint story has to come from somewhere else.
• Sign-in gets no easier by itself. The adapter authenticates with application passwords natively, and with OAuth through an optional Node.js proxy. The browser-based one-click sign-in that Claude, ChatGPT, Perplexity, Grok and the Gemini app expect is a plugin feature today.

How does Cowboy MCP fit with WordPress 7.2?

Cowboy MCP sits one layer above the framework, and since version 1.6.4 it plugs into it from both sides. Every allowed Cowboy tool is registered as a cowboy-mcp/* ability, so the adapter, wp ability run and the core abilities REST route can call Cowboy's 203 tools — with safe mode, dry runs, the audit log and the undo journal still applied — and, in the other direction, abilities that core and other plugins register appear to your agent as Cowboy tools. Both directions have a switch under Settings.

That means 7.2 is additive for a Cowboy site rather than a fork in the road. When the four core content abilities arrive, they show up as tools alongside Cowboy's own, with the caveat that abilities from other sources run their own permission checks and are not undoable. If you prefer to connect through the official adapter, Cowboy's tools are there too, and nothing you set up is wasted. And the plugin still runs on WordPress 6.2 and PHP 8.0 with no Composer or Node.js, so sites that will not be on 7.2 for a while lose nothing. The question to ask in December is the same as today: do you want a working toolset with undo, or a framework to build one on? You can have both.

FAQ