WordPress AI Team Publishes Its First Roadmap: Four Projects to Make WordPress AI-Native

If you’ve been following our recent news coverage, you’ve seen the pieces: Connectors API, Content Guidelines, Playground MCP, WordPress.com AI agents. Now here’s the picture they form. The WordPress AI Team has published its first official roadmap, outlining four projects that together aim to make WordPress a first-class platform for AI integration.

What Happened

The WordPress AI Team — a contributor team formed specifically to coordinate AI efforts across the ecosystem — has outlined four core projects:

1. PHP AI Client SDK (wp-ai-client): A provider-agnostic PHP library that gives developers a unified interface for calling any generative AI model. The WordPress-specific package (wordpress/wp-ai-client 0.1.0) handles credential management, the admin settings screen, and the core AI_Client::prompt() interface. Three official provider plugins — for OpenAI, Anthropic Claude, and Google Gemini — are already in the Plugin Directory.
2. Abilities API: Shipped as part of WordPress 6.9 in December 2025, this creates a machine-readable registry of WordPress capabilities. Think of it as a menu that AI tools can read to understand what actions are available on a given site — what content types exist, what the site can do, and what permissions are required.
3. MCP Adapter: A protocol adapter using the open Model Context Protocol that allows external AI assistants like Claude or ChatGPT to interact with WordPress sites. The goal is two-way integration: exposing WordPress functionality to AI tools, and eventually connecting WordPress to other MCP-compatible services.
4. AI Experiments Plugin: A sandbox plugin where the team and community can test new experiments — from workflow builders and embedded agents to WP-CLI support — before anything lands in core.

Why It Matters

This roadmap turns scattered AI efforts into a coherent strategy. Instead of every plugin developer building their own AI integration from scratch, WordPress is providing shared infrastructure: a standard way to authenticate (Connectors), a standard way to communicate with AI models (SDK), a standard way to describe site capabilities (Abilities API), and a standard protocol for external AI tools to interact with WordPress (MCP).

The approach is distinctly WordPress: open-source, provider-agnostic, and designed so that switching from one AI provider to another is a configuration change rather than a code rewrite. No vendor lock-in.

For the 42.5% of websites running WordPress, this could mean AI-powered features become as easy to add as installing a plugin — which is exactly the point.

What You Should Do

Plugin developers: Build against the wp-ai-client SDK and the Abilities API now. These are the standards WordPress is committing to. The SDK is on GitHub and the provider plugins are in the directory.

Site owners: No action needed yet. When WordPress 7.0 ships on April 9, the Connectors screen will be available in your admin under Settings. The real impact will come as plugins adopt these standards over the coming months.

Everyone: Follow the AI Team updates for weekly summaries. This is moving fast.

Sources

• WordPress AI Team Publishes First Roadmap — The Repository
• AI Contributor Weekly Summary — Make WordPress
• Introducing the Connectors API in WordPress 7.0 — Make WordPress Core