WordPress 7.0 RC1 just dropped, and the documentation makes the upcoming April 9th release look like a smooth glide. But if you have been following the AI Contributor group, you know the real work is happening in the trenches of the AI Experiments plugin. We aren’t just talking about a few buttons; we are talking about the foundation of how WordPress 7.0 AI Features will interact with the broader ecosystem.
As a developer who has seen “experimental” features break sites since the 4.x days, I’m cautiously optimistic. The team is currently balancing the “Try AI” callout with some heavy-duty infrastructure like the Model Context Protocol (MCP). Here is the technical breakdown of what actually matters for your production environments.
The Release Sprint: RC1 to Thursday, April 9
We are officially in the final stretch. While the target release remains April 9, 2026, there is ongoing internal debate regarding real-time collaboration. While that feature might impact the timing of RC2, it likely won’t move the final ship date. However, if the window narrows, expect some advanced connector filtering to be pushed to 7.1 to ensure stability.
If you haven’t started testing yet, now is the time. You should check out my WordPress AI Connector Plugins testing guide to see how your current stack handles the new API layers.
AI Experiments v0.7: Provenance and Classification
The AI Experiments plugin (v0.6 and the upcoming v0.7) is the real laboratory. One of the most critical additions is Content Provenance tracking via C2PA. In an era of deepfakes and AI-generated spam, being able to verify the origin of text and images directly in the media library is a massive win for enterprise users.
- Content Classification: Suggestions for tags and categories based on content, title, and excerpt. This is a huge “gotcha” for sites with messy taxonomies.
- Meta Description Experiment: Deep integration with existing SEO plugins to automate those tedious snippets.
- Content Resizing: Intelligent layout adjustments within the editor.
The MCP Adapter: Why Interop is the Real Story
The Model Context Protocol (MCP) is perhaps the most significant technical shift. Instead of building a custom “hack” or workaround for every LLM (Claude, ChatGPT, Gemini), MCP provides a standardized way for these models to discover WordPress site capabilities. Consequently, your site becomes a “resource” that AI can understand natively.
There was a bit of bike-shedding during the last meeting regarding naming conventions. Specifically, the team is debating whether to use wp_supports_ai() or wp_allows_ai() to align with Core patterns. Here is how that logic typically looks when you’re registering a custom connector:
<?php
/**
* Example of checking for AI support in WordPress 7.0
*/
function bbioon_check_ai_compatibility() {
// Checking if the current environment allows AI-driven features
if ( function_exists( 'wp_supports_ai' ) && wp_supports_ai() ) {
// Register your MCP adapter or AI connector here
bbioon_register_custom_ai_connector();
} else {
error_log( 'WordPress 7.0 AI Features are not enabled on this environment.' );
}
}
add_action( 'init', 'bbioon_check_ai_compatibility' );
Design and Branding: Avoiding the “Broken” Look
A funny but revealing moment in the summary: the team paused new plugin icons that featured a “breaking away” WordPress logo. Why? Because it looked like AI was literally breaking WordPress. It’s a good reminder that while we push the technical boundaries, the user perception of stability is everything. For more on this, read why the AI client ecosystem matters.
Look, if this WordPress 7.0 AI Features stuff is eating up your dev hours, let me handle it. I’ve been wrestling with WordPress since the 4.x days.
Takeaway: Standardize Now or Refactor Later
The move toward MCP and C2PA shows that the Core team isn’t just chasing the AI hype—they are building for longevity. Therefore, if you are building custom AI integrations today, ensure you are following the Gutenberg 22.7 Content Guidelines. Failing to align with these standards now will only lead to a massive refactor once 7.1 drops.
