WordPress Is Quietly Becoming an AI Platform
WordPress 7.0, released May 20, 2026, did something historic for the CMS: it put native AI infrastructure into core. The AI Client, the Abilities API, and AI Connectors gave WordPress a standardized, provider-agnostic way to talk to external AI models — OpenAI, Google Gemini, Anthropic Claude, and others — without every plugin author writing their own API wrapper.
Since then, the work has continued on two tracks: the WordPress AI plugin (the fast-moving feature plugin where new AI capabilities land first) and core itself. Here’s where the roadmap stands as of early October 2026, based on the Core AI team’s public notes: embeddings, the MCP adapter, a Secrets API headed for core, and WordPress 7.2 on the horizon.
What’s Already Shipped
WordPress 7.0: The AI Foundation
Three pieces landed in core with 7.0:
- AI Client — the foundational API for running AI programmatically inside WordPress, starting with generation capabilities for plugin authors.
- Abilities API — a way for plugins, themes, and core to register their capabilities in formats readable by both humans and AI agents, so AI tools can discover and use plugin functionality automatically.
- Connectors — a framework for registering and managing connections to external AI services, starting with API-key authentication.
The design principle matters: no data leaves your site until you configure a connection under Settings → Connectors and explicitly enable it. Provider-agnostic from day one.
AI Plugin 1.3.0: The Fast Lane
The WordPress AI plugin moves faster than core. Version 1.3.0 shipped August 18, 2026, with per-ability filters for customizing system instructions and prompts, a public log_ai_request() API for recording AI activity, custom provider support, and — relevant to the roadmap — embedding-generation code from the PHP AI Client as groundwork for environments that support embeddings. Development has moved to 1.4.0.
The Roadmap: What’s Coming
Embeddings and Semantic Search
Embeddings represent content as vectors, enabling meaning-based search across a site — search that understands what you meant, not just the keywords you typed. The PHP AI Client’s embedding support didn’t land in WordPress 7.1, but the team is pushing to merge it well ahead of the 7.2 beta so there’s time for upstream review. The 1.3.0 plugin groundwork means the capability is already being exercised in the feature plugin.
For site owners, semantic search is the user-facing payoff: visitors finding the right article even when they phrase the query differently. For developers, embeddings unlock recommendation features, related-content engines, and agent workflows that reason over site content.
MCP Adapter: WordPress as a Tool for AI Agents
The MCP Adapter turns registered WordPress abilities into MCP (Model Context Protocol) tools, so external AI agents — in IDEs, assistants, or standalone clients — can call your site’s functionality directly. Version 0.3.0 brought transport, observability, and error-handling improvements.
The roadmap calls for distributing the adapter through the WordPress.org Plugin Directory and reducing the setup required to enable MCP access. The framing from the AI team: “WordPress as a tool” in the agent ecosystem. Instead of agents scraping your site, they call its abilities through a consistent auth and permissions story.
Secrets API → WordPress 7.2 Core
The AI team has aligned on a proposal to merge the Secrets API — already available in the AI plugin — into WordPress 7.2 core, and is seeking community feedback. This gives plugins a standard, secure way to store credentials and API keys instead of plaintext options, with a documented interface for detecting feature availability so existing code can migrate cleanly.
This is unglamorous infrastructure, and it’s exactly the kind of thing that needs to be in core. Every AI integration needs credential storage; a standard API means plugins stop reinventing it insecurely.
WordPress 7.2: The Timeline
The 7.2 roadmap also includes a new default theme (Ipsum, marking a move away from year-based theme names), media and performance work, and an extensible site editor. The first beta is planned for around October 20–22, with the final release around December 8–10.
One honest caveat from the roadmap itself: AI-related development continues through the AI plugin rather than being guaranteed for any given core release. Features land in core when they’re ready, not on a marketing schedule. Track the Make WordPress AI blog for what actually merges.
What This Means for Site Owners
Short term (now): If you run a WordPress site, the AI features that matter today live in plugins, not core. The core infrastructure is plumbing for developers. You don’t need to do anything, but you should know the plumbing exists — it’s why AI features in plugins are getting better and more consistent.
Medium term (7.2 and beyond): Expect semantic search, agent-accessible sites via MCP, and more standardized AI features arriving through the usual update flow. The Connectors framework means you’ll configure AI providers in one place (Settings → Connectors) instead of pasting API keys into five different plugins.
If you’re a developer or agency: the Abilities API is the thing to learn. Registering your plugin’s capabilities as abilities makes them automatically available to AI agents through the MCP adapter. That’s a new distribution surface for plugin functionality, and early movers will define the patterns.
A note on the security release: WordPress 7.1.2 (September 22, 2026) patched the critical CVE-2026-87902 vulnerability. If you haven’t updated yet, do that before thinking about AI features — security first, always.
The Bigger Bet
WordPress powers over 43% of the web. If a meaningful fraction of those sites become agent-accessible through standardized abilities and MCP, WordPress becomes one of the largest surfaces in the agentic web — not as a chatbot bolt-on, but as infrastructure. The roadmap is methodical rather than flashy: embeddings, credential storage, protocol adapters. That’s how platforms get built.
Source: Make WordPress AI team updates — the Core AI team’s public notes. Release dates are targets and can shift; follow the Make blog for confirmations.
Official source: WordPress.org
Frequently Asked Questions
What AI features are in WordPress core right now?
WordPress 7.0 (May 2026) added the AI Client, Abilities API, and Connectors framework to core. These are developer infrastructure — standardized ways for plugins to use AI models and register capabilities for AI agents — rather than end-user features.
What is the WordPress AI plugin?
A feature plugin where new AI capabilities land and mature before (potentially) merging into core. Version 1.3.0 shipped August 2026 with ability filters, AI request logging, custom providers, and embeddings groundwork.
What are embeddings in the WordPress context?
Embeddings represent content as vectors, enabling meaning-based (semantic) search across a site. The PHP AI Client’s embedding support is targeted for WordPress 7.2, with groundwork already in the AI plugin.
What is the MCP Adapter for WordPress?
It bridges WordPress abilities to the Model Context Protocol, letting external AI agents (in IDEs, assistants, etc.) discover and invoke your site’s registered functionality through a consistent auth/permissions story.
What is the Secrets API?
A proposed standard API for secure credential and API-key storage in WordPress, already in the AI plugin and proposed for WordPress 7.2 core. It replaces ad-hoc plaintext secret storage in plugin options.
When is WordPress 7.2 coming?
First beta is targeted around October 20–22, 2026, with final release around December 8–10. Dates are targets and can shift.