WordPress just made its boldest move into AI-powered development. Between January and February 2026, Automattic and the WordPress community shipped a rapid-fire series of AI integrations that fundamentally change how developers, agencies, and site builders work with the platform. Combined with the upcoming WordPress 7.0 release planned for April, which proposes native AI query capabilities in core, we are looking at the most transformative period in WordPress history since Gutenberg.
This is not one announcement. It is a coordinated infrastructure-first strategy: build the foundation, then ship products on top. Here is everything that landed, why it matters, and what you should do about it.
Layer 1: PHP AI Client, AI for All of PHP
The PHP AI Client is a provider-agnostic SDK that lets any PHP project communicate with any generative AI model through a uniform API. While stewarded by the WordPress AI Team, it is deliberately WordPress-agnostic.
Install it with Composer:
composer require wordpress/php-ai-client
The API is clean and fluent:
use WordPress\AiClient\AiClient;
// Text generation with any compatible model
$text = AiClient::prompt('Write a product description.')
->generateText();
// Use a specific provider
$text = AiClient::prompt('Summarize this article.')
->usingProvider('anthropic')
->generateText();
// Image generation
$image = AiClient::prompt('A WordPress logo in neon style.')
->generateImage();
// With system instructions and temperature
$text = AiClient::prompt('Write a blog intro.')
->usingSystemInstruction('You are a WordPress expert.')
->usingTemperature(0.8)
->generateText();
It supports OpenAI, Google (Gemini), Anthropic (Claude), and any provider that follows standard API patterns. PSR-14 event dispatching is built in for logging and monitoring. This was last updated on February 18, 2026, and active development is ongoing.
Layer 2: WP AI Client, AI Native in WordPress
The WP AI Client wraps the PHP AI Client with WordPress-specific features:
- Admin Settings Screen: Go to Settings → AI Credentials in wp-admin to configure API keys for Anthropic, OpenAI, Google, or any supported provider. No code required.
- Automatic Credential Wiring: API keys stored in WordPress database options are automatically passed to the PHP AI Client.
- JavaScript API: A client-side
wp.aiClientAPI with a similar fluent prompt builder, powered by REST endpoints under the hood. - Access Control: A
prompt_aicapability controls who can make AI queries. By default, only administrators have access. Sites can customize this per role.
PHP usage in a plugin or theme:
use WordPress\AI_Client\AI_Client;
$text = AI_Client::prompt('Write a haiku about WordPress.')
->generate_text();
echo wp_kses_post($text);
JavaScript usage in the block editor or admin:
const text = await wp.aiClient
.prompt('Write a haiku about WordPress.')
.generateText();
console.log(text);
This is proposed for core merge in WordPress 7.0. If it lands, every WordPress plugin and theme gets native AI capabilities without bundling their own SDK or locking into a single provider. Updated February 17, 2026.
OAuth 2.1 for AI Agents (January 2026)
The security foundation. WordPress.com introduced OAuth 2.1 authentication specifically designed for AI agents. This enables AI tools to connect to WordPress.com sites securely, with proper scoping and permission controls. Without this, everything that followed would have been a security risk.
WordPress MCP Adapter (February 2026)
The Model Context Protocol (MCP) Adapter implements MCP within a WordPress site and lets AI tools like Claude Desktop, Claude Code, Cursor, and VS Code discover and call WordPress Abilities directly.
Built on the Abilities API from WordPress 6.9, this turns your WordPress site into an MCP server. If you have been using MCP tools with Claude Code, the WordPress MCP Adapter takes this to the next level.
WordPress.com Claude Connector (February 5)
The first official integration between a WordPress host and Anthropic. The Claude Connector uses OAuth 2.1 to let Claude query your site’s analytics, content, and settings directly. Backed by both Automattic and Anthropic.
Content Guidelines (Gutenberg Experiment)
Content Guidelines gives site owners a first-class space in the editor to define editorial rules. AI agents writing or editing content can read these guidelines natively, producing content that matches your voice and standards from the start.
Claude Cowork Plugin + Agent Skills (February 13)
The Claude Cowork plugin turns a conversation with Claude into a fully built WordPress site, complete with block themes with theme.json, templates, and style variations. The accompanying Agent Skills repository includes wp-playground, which lets AI agents run WordPress via the Playground CLI and verify their own work.
WordPress Studio 1.7.0
WordPress Studio expanded its CLI for full compatibility with AI-assisted dev tools. Local WordPress development now works seamlessly with Claude Code, Cursor, and other AI coding assistants.
WordPress.com AI Assistant (February 17)
The product layer built on all this infrastructure. A persistent editor AI offering:
- Design changes through conversation
- Content editing, expansion, and summarization
- Image generation and editing within the editor
- Translation directly in the editor
- Native block editor integration
Available on Business and Commerce plans.
- PHP AI Client: Any PHP code can talk to any AI model
- WP AI Client: WordPress plugins and themes get native AI with access control
- Abilities API (WP 6.9): WordPress exposes what it can do in a standardized way
- MCP Adapter: External AI tools discover and call those abilities
- OAuth 2.1: AI agents authenticate securely
Together, this creates two-way AI communication. WordPress can call AI (via WP AI Client), and AI can call WordPress (via MCP Adapter). This is what turns WordPress from an AI-compatible CMS into an AI-native platform.
The approach is infrastructure first, then product on top. Every product feature, from Claude Cowork to the AI Assistant, builds on the same foundational layers that third-party developers can use.
| Plugin | What It Does | AI Integration |
|---|---|---|
| AI Workflow Automation Hub | Registers 70+ abilities across 9 modules | Built-in MCP server for WP 6.9 Abilities API |
| AI Engine | Chatbot and AI framework | Exposes WordPress tools to ChatGPT, Claude via MCP |
| Bit Flows AI Agent | Agentic workflows | Autonomous decision-making for leads, content, support |
| AI Puffer | Content generation and voice | GPT-5, Gemini, real-time voice input |
- Add
wordpress/php-ai-clientto your Composer dependencies. Start building AI features into your plugins using the provider-agnostic SDK today. - Test the WP AI Client on a staging site. The
prompt_aicapability and admin settings screen are production-ready patterns. - Register abilities in your plugins through the Abilities API. This makes your plugin’s functionality discoverable by AI agents via the MCP Adapter.
- Try wp-playground for AI-assisted development. Agents that test their own code in disposable WordPress instances is a genuine productivity multiplier.
For Agencies
- Test Claude Cowork for rapid theme prototyping. Offering clients a working prototype in the first meeting changes your sales process.
- Install the MCP Adapter on staging and connect it to Claude Code. Build content pipelines that handle generation through publishing.
For Site Owners
- Update to WordPress 6.9. The Abilities API is the foundation everything builds on.
- Set up Content Guidelines in your editor so AI tools follow your editorial voice.
- Check if your plan supports the AI Assistant (Business or Commerce on WordPress.com).
A provider-agnostic PHP SDK (wordpress/php-ai-client) that lets any PHP project communicate with AI models from OpenAI, Anthropic, Google, and others through a uniform API. While maintained by the WordPress AI Team, it works in any PHP project.
What is the WP AI Client?
A WordPress-specific wrapper built on the PHP AI Client. It adds an admin settings screen for API credentials, automatic credential wiring, a JavaScript API (wp.aiClient), and role-based access control via the prompt_ai capability. Proposed for core merge in WordPress 7.0.
What is the WordPress MCP Adapter?
The MCP Adapter implements the Model Context Protocol within a WordPress site, letting AI tools like Claude Code, Cursor, and VS Code discover and interact with WordPress through the Abilities API.
When is WordPress 7.0 releasing?
WordPress 7.0 is planned for April 2026 with a beta in mid-March. It is expected to include the WP AI Client in core, expanded Abilities API, unified design tokens, and real-time collaboration features.
Can I use AI in my WordPress plugins today?
Yes. Install wordpress/php-ai-client via Composer and start making AI queries immediately. For WordPress-specific features like admin settings and JavaScript API, use the WP AI Client plugin. Both are available now on GitHub.
For more on AI tools for WordPress, read our guide on AI tools every developer needs in 2026 and our preview of WordPress 7.0.
Abilities API AI in WordPress Claude MCP Protocol WordPress 7
Last modified: February 19, 2026








