WordPress 7.0 Beta 1 dropped today, 19 February 2026, and it includes something no other major CMS has done: built-in AI agent support. The MCP Adapter ships with core, letting AI tools like Claude Desktop, Cursor, and VS Code interact with your WordPress site directly through Anthropic's Model Context Protocol.
The final stable release is targeted for 9 April at WordCamp Asia. But the beta is available for testing right now, and the AI integration is the part that changes everything.
Here's why this matters more than the real-time collaboration features most outlets are leading with, and what UK businesses running WordPress should be doing about it.
What the MCP Adapter Actually Does
The foundation is the Abilities API, which shipped in WordPress 6.9 last year. It lets plugins, themes, and core register their capabilities in a machine-readable format. WordPress 6.9 shipped with three default abilities: core/get-site-info, core/get-user-info, and core/get-environment-info.
The MCP Adapter translates those abilities into the Model Context Protocol, the open standard that Anthropic created for connecting AI systems to external tools. As Jonathan Bossenger explained in the WordPress Developer Blog:
"If WordPress supported MCP, it would be possible to give AI secure access to all your orders for the year."
That's the practical version of what this enables. An AI agent connected to your WordPress site can read product data, pull analytics, generate content drafts, and trigger plugin actions. All within WordPress's existing permission system. The agent can only do what the logged-in user is authorised to do.
This isn't theoretical. The MCP Adapter is on GitHub now, and it already works with Claude Code, Claude Desktop, Cursor, and any other MCP-compatible client. For those of us who build WordPress sites daily, that's a meaningful shift in how we'll work.
The Features Most Sites Will Notice
The MCP Adapter is the headline for developers. But WordPress 7.0 Beta 1 packs several other changes that affect every WordPress site.
Real-time collaboration is the feature WordPress has been chasing for years. Multiple users can now edit the same post simultaneously, seeing each other's cursors and changes in real time. It works like Google Docs, but inside the block editor. For agencies and editorial teams, this kills the "someone else is editing this post" lockout message.
Per-block custom CSS finally gives site builders precise control. You can now add CSS to a specific block instance through the Advanced sidebar, and a .has-custom-css class gets applied automatically in both the editor and the frontend. No more hunting through theme stylesheets to style one particular section.
Viewport-based block visibility expands on what 6.9 started. You can now control which blocks appear on mobile, tablet, or desktop through the block inspector panel. This is the kind of responsive control that previously required CSS helper classes or page builder features.
The admin interface refresh introduces view transitions between screens. It's the first visual update to the WordPress admin since the block editor landed in 2018. Smooth page transitions replace the old full-page reloads, and the design aligns with the newer WordPress Design System.
The post editor is also now always iframed, regardless of block API version. This creates a consistent editing experience and properly separates UI styles from block and theme styles. Developers who relied on the old non-iframed behaviour will need to check their blocks. WordPress has published a migration guide for iframe editor compatibility.
The Page Builder Question
There's an elephant in the room. Roughly 40% of WordPress sites use page builders like Elementor, Divi, WPBakery, or Bricks instead of Gutenberg. The MCP Adapter works through the REST API, and as one developer pointed out: "When you ask the REST API to read a Divi page, you get raw shortcode soup. When you try to write to it, you're likely to break the layout entirely."
For sites built on Gutenberg, the AI integration is immediate and useful. For page builder sites, it's limited to content and settings that go through the standard REST API. Plugin developers are already building bridges (Respira, for example, adds module-level awareness for eight major builders), but the gap exists today.
If you're planning a new WordPress build, this is another reason to go with the block editor. If you're on a page builder, the collaboration and admin features still work, but the AI agent capabilities are restricted.
What This Means for Your Business
WordPress powers over 40% of the web. When it adds native AI agent support, it's not a niche developer feature. It changes how content gets managed, how sites get maintained, and how businesses interact with their own web presence.
Three things to consider.
Don't install Beta 1 on your live site. It's a beta for a reason. Test it on a staging environment first. As Matias Ventura noted in the planning post, WordPress 7.0 is "a gathering point for contributors, not a roadmap or commitment." Features can still change before the 9 April release.
The AI agent angle matters more than collaboration. Real-time editing is useful for teams, but the MCP integration is structural. It positions WordPress as the first major CMS where AI tools can read your site's data, trigger actions, and build on your existing plugin ecosystem. For AI visibility, that's a shift from making your site visible to AI systems to giving AI systems direct access to your site's capabilities.
If your business already uses AI discovery files to make your site findable by AI, the MCP Adapter takes it a step further. Discovery files tell AI who you are. The Abilities API tells AI what your site can do. Those are complementary layers, and WordPress 7.0 is the first CMS to support both.
Talk to your hosting provider and developer now. April isn't far off. Your hosting provider needs to confirm PHP 8.x compatibility (WordPress 7.0 drops support for PHP 7.2 and 7.3). Your developer needs to test your theme and plugins against the beta. Your agency needs to evaluate whether MCP integration opens new workflows for content management.
Our sister site has a detailed breakdown of the full WordPress 7.0 feature list from a hosting perspective, including what managed WordPress hosts should be preparing for.
Release Timeline
| Milestone | Date |
|---|---|
| Beta 1 | 19 February 2026 (today) |
| Beta 2-4 | 26 February to 12 March 2026 |
| Release Candidate 1 | 19 March 2026 |
| Release Candidates 2-3 | 26 March to 2 April 2026 |
| Stable Release | 9 April 2026 (WordCamp Asia) |
Four beta releases, at least three release candidates, then the stable launch at WordCamp Asia in April. That's a compressed timeline, and it means plugins and themes need testing sooner rather than later. Beta 2 has since shipped with a new Connectors page that lets site owners configure OpenAI, Claude, and Gemini directly from the WordPress admin.
Frequently Asked Questions
When is the WordPress 7.0 final release?
9 April 2026, timed to coincide with WordCamp Asia. Beta testing runs from 19 February through mid-March, followed by release candidates until early April.
What is the WordPress MCP Adapter?
The MCP Adapter bridges WordPress's Abilities API to Anthropic's Model Context Protocol. It lets AI tools like Claude Desktop, Cursor, and VS Code discover what your WordPress site can do and interact with it directly, all within existing user permissions.
Should I install WordPress 7.0 Beta 1 on my live site?
No. Beta releases are for testing only. Set up a staging environment and test your theme, plugins, and custom code there. Features and APIs can still change before the stable release on 9 April.
Does the MCP Adapter work with Elementor, Divi, and other page builders?
Only partially. The MCP Adapter works through the REST API, which handles standard WordPress content well but struggles with proprietary page builder formats. Sites using Gutenberg get full AI agent integration. Page builder sites can still use MCP for settings, user data, and standard content, but not for builder-specific layouts.
What AI tools can connect to WordPress 7.0?
Any MCP-compatible client. That currently includes Claude Desktop, Claude Code, Cursor, VS Code (with the MCP extension), and the WordPress.com Claude Connector. More clients are expected as MCP adoption grows across the AI ecosystem.
Is real-time collaboration in WordPress 7.0 production-ready?
It's in beta. The multi-user editing feature works in the block editor and shows live cursors and changes, similar to Google Docs. It still needs testing across different hosting environments and with complex post types before the April release. Don't rely on it for production workflows until the stable version ships.
What PHP version does WordPress 7.0 require?
WordPress 7.0 drops support for PHP 7.2 and 7.3. You'll need PHP 7.4 or higher, though PHP 8.1 or later is recommended. Check with your hosting provider now, as some shared hosts still default to older PHP versions.
How does the MCP Adapter relate to AI discovery files?
They're complementary layers. AI discovery files (like llms.txt and ai.json) tell AI systems who your business is, what you do, and how to represent you. The MCP Adapter tells AI agents what your WordPress site can do and lets them take actions. Together, they make your business both visible to and usable by AI systems.
Is Your WordPress Site Ready for AI Agents?
WordPress 7.0 lets AI agents interact with your site directly. But they need to find you first. AI discovery files make sure Claude, ChatGPT, and Gemini know who you are and what you do.
Check Your AI Visibility
