WordPress 7.2’s AI Roadmap Just Landed. Write Abilities, Plugin Directory MCP, and Native Track-Changes Are the December Story.
Nobody's Talking About the Right Part
The WordPress 7.2 roadmap landed September 18, 2026. Nine hundred words cover design and editor changes — the admin gets SVG icons, revision history tracks post titles, a new default theme called Ipsum ships as a blank canvas. Useful improvements. None of them are why content teams should open this tab.
The AI section lists nine bullet points. Eight of them move the needle on what an AI system can actually do inside a WordPress install. Beta 1 targets October 20–22, 2026. Final release is December 8–10. Ten weeks.
Write Abilities Change the Workflow
WordPress 7.0 launched the Abilities API in May. What it shipped were read abilities. core/read-content. core/read-users. core/read-settings. An AI agent connected through MCP could look at your site. It could not touch anything.
The 7.2 roadmap changes that direction. The AI team committed to exploring write abilities and a CRUD-style structure for content operations. When those land, a connected AI agent can create a draft, update a post, or publish content under configurable permission scopes — not as a free agent, but under a formal Abilities API registration that site administrators control.
For teams running AI-assisted content workflows today, this is the architectural shift that turns WordPress from a publishing destination into an active participant in automation pipelines. A WordPress install that can be briefed through natural language and produce a draft without a human opening the block editor is a fundamentally different kind of infrastructure than the one running on most sites right now.
The team is explicit that write abilities land in the AI plugin first, not in core, with no guarantee they make the December cut. The most direct way to influence that: install the AI plugin, use it on a real site, and file structured issues on the GitHub repository. The AI contributor weekly summary from September 16 said as much plainly.
MCP Adapter Is Leaving the Beta Corner
The Model Context Protocol Adapter has been running as a standalone repository since WordPress 7.0. Getting it running on a client site still required enough server-side setup to keep it outside most agency production stacks. That changes with 7.2.
The roadmap targets Plugin Directory distribution for the Adapter. Published to WordPress.org, updated through the standard auto-update flow, reviewed by the plugin team. That distribution path is the trust signal required to clear most client security reviews. An Adapter in the Plugin Directory is an Adapter a non-developer administrator can install.
Alongside distribution, the roadmap targets seamless MCP access through the AI plugin settings screen. Enable MCP through Settings > AI, install the Adapter from within that screen, configure which abilities are exposed. No PHP configuration files. No manual JSON setup. The gap between "a developer configured this on a staging server" and "a marketing manager toggled this on" is what 7.2 is designed to close.
The PHP-MCP schema is already being updated to version 0.2.0, with three PRs under review as of the September 16 AI team summary. Backward compatibility through client-server version negotiation is being built in. When the Plugin Directory version ships, it lands into an already-updated protocol layer.
The AI Plugin Also Got a Course This Week
On September 18, the official AI-Powered WordPress course went live on Learn WordPress. It covers connecting an AI provider through the Connectors screen under Settings, using the editorial tools that shipped in WordPress 7.0 and 7.1, and understanding how the Abilities API works in practice. Not a developer course. It targets site owners and content teams.
For teams evaluating whether to adopt the AI plugin before the 7.2 beta cycle opens, this is the onboarding resource that did not exist a week ago.
Notes Is Getting Suggestion Mode. That Is Track Changes.
The collaboration headline in 7.2 is Notes — and the centerpiece is suggestion mode. Reviewers can leave proposed block-level edits that editors accept or reject directly inside the block editor. Emoji reactions ship alongside it. A dedicated keyboard shortcut in the block toolbar surfaces the feature without navigating menus.
Real-time multi-user editing is explicitly off the roadmap for 7.2. The core team is rebuilding that from scratch as a server-aware system, routing all updates through WordPress rather than syncing peer-to-peer in the browser. The decision keeps the server in control of content attribution and permission checks — which matters as soon as AI agents enter the editorial loop. They decided not to list real-time collaboration on the 7.2 roadmap until the server-aware architecture is ready.
Suggestion mode through Notes is what ships in December. For content teams currently routing article feedback through Google Docs or leaving comments in Slack before someone manually applies edits in WordPress, this is the native answer.
Embeddings and Streaming: The Infrastructure No One Leads With
Two roadmap items are not user-visible features. They are infrastructure that everything else builds on.
Shared embedding support in the AI plugin means generation, storage, and background synchronization of vector embeddings derived from your site content. The output: semantic search and AI responses grounded in your actual published material rather than generic model knowledge. For sites running news sections, product documentation, or industry-specific authority content, this matters directly. An AI assistant answering visitor questions draws from your indexed content as its source of truth rather than hallucinating answers from training data.
Streaming support in the PHP AI Client means generated text displays as it arrives rather than after a full-response delay. Time-to-first-byte for AI writing features drops visibly. The team flagged this as groundwork for broader WordPress and hosting support — not just a plugin-layer change. Sites on managed WordPress hosting where the host controls the PHP environment will eventually benefit from this at the server level.
Neither of these will appear in a changelog in a way that sounds impressive. Both of them are what makes December's release more capable than August's.
What Content Teams Should Do Before October 22
Beta 1 opens October 20–22. That window matters most for content teams with real publishing workflows, not just developers testing on local environments.
Install the AI plugin on a staging site now. Enable the Custom Abilities toggle under Settings > AI > Admin Experiments. Run the AI-Powered WordPress course on Learn WordPress to understand what the Connectors screen controls. Then use the plugin on content that reflects your actual workflow — news drafts, product updates, scheduled articles — and file specific GitHub issues when behavior doesn't match expectations.
The WordPress AI team is building infrastructure for human-assisted AI content workflows. Suggestion mode through Notes, scoped write abilities with auditable agent identities, MCP access through a settings toggle — these are all designed around the same premise: an AI system earns permission one capability at a time, and a real person stays in the decision loop at every meaningful point.
That is not a platform limitation. That is the design.
FAQ
When does WordPress 7.2 release? Beta 1 is scheduled for October 20–22, 2026. The final release targets December 8–10, 2026.
What is the WordPress MCP Adapter? The MCP Adapter translates WordPress Abilities into Model Context Protocol format, allowing AI assistants like Claude and ChatGPT to discover and invoke WordPress capabilities as tools. WordPress 7.0 shipped the Abilities API foundation; the 7.2 roadmap targets Plugin Directory distribution for the Adapter so it installs and updates like any other plugin.
Will write abilities in WordPress 7.2 allow AI to publish content automatically? Not without explicit administrator configuration. The Abilities API requires a formal registration and the AI plugin's Custom Abilities toggle controls what is exposed externally. The agent identity and delegation work on the 7.2 roadmap is specifically designed to gate write operations behind auditable, revocable permissions — keeping the site owner in control of what any agent is allowed to do.
