AI Tech NewsYour portal to artificial intelligence
Home / WordPress 7.0 Puts AI in Core: MCP Adapter, AI Client, and Abilities API Explained
Generative AIAI ToolsAI Industry

WordPress 7.0 Puts AI in Core: MCP Adapter, AI Client, and Abilities API Explained

WordPress powers roughly 40% of the web. On May 20, 2026, it released version 7.0 — codenamed "Armstrong" — and did something it had never done before: baked AI infrastructure directly into core.

The short version: WordPress is no longer just a platform that supports AI plugins. It's now providing a standardized, secure foundation for AI to interact with your site.

What Changed in One Sentence

WordPress 7.0 ships with a native AI Client, Abilities API, official MCP Adapter, and a centralized Connectors Hub — ending the fragmented era of every plugin managing its own AI connection, and opening the door to AI agents operating directly on WordPress sites.

Why This Is Different From Before

Before 7.0, AI in WordPress meant third-party plugins. That created three persistent problems:

  • Every plugin managed its own API keys separately.
  • AI capabilities couldn't be shared or composed across plugins.
  • There was no unified security or permissions model.

WordPress 7.0 solves all three — not by bundling AI features, but by building the underlying framework that makes them possible.

Breaking Down the Key Features

1. AI Client and Connectors Hub

The Connectors Hub is a centralized dashboard where administrators can authenticate and manage connections to multiple AI providers — OpenAI, Anthropic (Claude), and Google Gemini — in a single location.

Previously, every AI plugin required its own API key setup. Now you configure it once, and any authorized component on the site can use it.

Developers access these connections through the WP AI Client SDK, which provides a consistent, provider-agnostic interface for making AI requests.

2. Abilities API

The Abilities API lets plugins register specific capabilities — things like "create a post," "generate an excerpt," or "update a custom field."

AI agents can then discover these registered abilities and invoke them within defined permission boundaries.

This design matters for security: instead of AI tools accessing the database directly, they interact through well-defined functional interfaces. The scope is bounded. The risk is lower.

3. Official MCP Adapter

This is the feature that generated the most discussion in the developer community.

MCP (Model Context Protocol) is a standardized way for AI models to communicate with external systems. WordPress 7.0 ships with an official MCP Adapter that allows external AI tools — including Claude Code, Cursor, and Codex — to:

  • Read posts, pages, and media from a WordPress site.
  • Create or update content based on instructions.
  • Perform permitted operations within a secure, permissioned boundary.

In practical terms: you could tell Claude "translate this post into French and update the site" — and it could do that directly, without you copying and pasting anything manually.

4. Opt-in User-Facing AI Features

Core provides the infrastructure, not the features. User-facing AI tools — writing assistance, image generation, bulk alt-text generation in the Media Library — are delivered through an official, optional AI plugin that administrators can choose to install or skip.

This design respects user choice: the framework is always there, but no one is forced to use AI features they don't want.

A Few Things Worth Noting

Real-Time Collaboration Was Delayed

The 7.0 release was widely anticipated to also include multi-user real-time co-editing (Gutenberg Phase 3). It was removed shortly before launch due to performance and server load concerns. That feature is expected in a future release.

WordPress 7.1 Is in Progress

The 7.1 development cycle is currently underway, with a full release expected in August 2026. The AI Client is planned to gain streaming support and embeddings — capabilities that will make it significantly more useful for semantic search, content recommendations, and real-time AI generation.

Security Is a Growing Concern

The rapid expansion of AI plugins has prompted real security scrutiny. A recent vulnerability (wp2shell) was patched in WordPress 7.0.2. The community is increasingly treating AI plugins as a significant security surface area — not just a feature layer. Site owners running AI-related functionality should monitor security advisories closely.

What Does This Mean for You?

If you're a content editor or site administrator:

  • More AI-assisted tools are coming to your admin dashboard.
  • Managing AI provider credentials gets simpler through the Connectors Hub — no more jumping across plugin settings pages.

If you're a developer:

  • The WP AI Client SDK removes the need to write custom connection logic for each AI provider.
  • The MCP Adapter opens a new class of automation — AI tools that can operate on WordPress sites directly, enabling complex AI-driven workflows.

If you're a site owner who doesn't want AI:

  • Core only provides infrastructure. AI-facing features require separate installation and aren't forced on anyone.

Our Take

WordPress 7.0 and the Drupal AI Initiative are converging on the same conclusion from different angles: the right way to bring AI into a CMS isn't to ship AI features — it's to build the infrastructure that makes AI features possible, controllable, and safe.

For WordPress, the challenge is scale. The platform serves everyone from personal bloggers to enterprise e-commerce operations. That diversity makes any core architectural decision controversial, and the community response has been mixed — some welcoming standardization, others concerned about the platform's direction.

That debate will continue. But the technical signal is clear: AI infrastructure is now part of WordPress core, not an afterthought. Future versions of the platform will be built around this assumption.

Sources