WordPress 7.0 AI is moving out of the experimental phase and into core architecture. I have been following the contributor chats, and the April 8th meeting was mostly plumbing rather than hype. If you have been skeptical about where AI fits into the WordPress lifecycle, the two things worth your attention are the Connectors API and the AI Client.
The AI client is priority one for 7.0
The AI Client is the top priority for the 7.0 release cycle, and it is bigger than a generate-text button in the editor. It gives any plugin one standard way to talk to a large language model, which keeps every plugin developer from bundling their own bloated SDK for OpenAI or Anthropic.
I have watched a site fall over because three plugins each loaded a different version of Guzzle to make their API calls. Centralizing the transport layer takes that whole class of conflict off the table. The team has also said it will turn bug reports around quickly while early adopters stress-test the client on real sites.
What the Connectors page is really for
The new Connectors page (under Settings > Connectors) is a single interface for credentials, and it is deliberately not called AI Connectors. It is meant to hold credentials for any third-party service, including Akismet, WooCommerce Tax and Mailchimp. One standard place for API keys would clean up a decade of scattered settings screens.
If you build for regulated clients, a hospital or a law firm, the architecture supports picking HIPAA-compliant providers. There is also a constant that acts as an emergency brake and switches AI features off across the entire site.
// The "Off Switch" for AI Features
// Add this to your wp-config.php to completely disable AI capabilities
define( 'WP_AI_DISABLED', true );
// Example: Registering a custom connector (Hypothetical Connectors API usage)
add_action( 'init', function() {
if ( function_exists( 'bbioon_register_connector' ) ) {
bbioon_register_connector( 'my-custom-service', [
'label' => __( 'Custom Analytics' ),
'description' => __( 'Manage your API credentials for deep analytics.' ),
'group' => 'analytics',
] );
}
} );Version 0.7.0 and the new settings UI
The AI plugin reaches version 0.7.0 this week, and the notable change is a settings UI built on a data-form structure. Sub-settings get generated automatically instead of being hand-built in CSS, and nothing about the user experience breaks in the process. That schema-driven approach is what a stable 1.0 needs.
I went further into what this means day to day in a piece on finalizing the WordPress 7.0 AI architecture.
The MCP adapter at 0.5.0
The Model Context Protocol (MCP) adapter is close to version 0.5.0, and there is still an argument about whether it ships as a Composer package or a standalone plugin. I lean standalone for the sake of non-technical users, though on enterprise builds a Composer package is the only safe way to manage the dependency. If MCP is new to you, start with my piece on managing your site via MCP agents.
If this AI work is eating your dev hours, I can take it on. I have been working with WordPress since the 4.x days, and I know how to put these APIs in without breaking a legacy codebase.
Where the roadmap points
Stability comes first on this roadmap. The leadership change, with Jason Adams moving to Director of AI at Automattic, and the emphasis on the AI Handbook’s philosophy both point the same way: the project is building infrastructure meant to last rather than chasing a trend. The WordPress AI Handbook and the MCP Spec are where the official documentation lands.
