WordPress 7.0 “Armstrong” shipped on May 20th. One of its most talked-about features: a native AI Client built directly into the admin panel. No extra plugins, no complex setup. You write, the AI responds, it acts inside your WordPress.
Sounds good. And in part, it is.
But there’s a detail missing from the headlines: to use it, you need an API Key from an AI provider — which means an additional monthly bill on top of what you already pay for your site and your AI tools.
If you’re already paying for Claude Pro, you’re paying twice for a fraction of the capability.
How the WP 7.0 Native AI Client Works
WP 7.0 introduces three AI-related things:
- WordPress Abilities API: a native system for plugins to register “abilities” — actions the AI can execute inside WordPress (create posts, update meta, read content, etc.)
- Connectors Hub: a repository of connectors to external services
- Native AI Client: an interface inside the WP admin panel that connects to an AI provider via API
The AI Client is the visible interface. And for it to work, you need to connect it to a provider: OpenAI, Anthropic, Google, etc. That requires your own API Key, with its own token-based or usage-based billing model.
If your team already has Claude Pro and now also needs an Anthropic API Key for the WP AI Client, you’re paying twice for the same capability — and the API version typically has less context, no persistent memory, and none of the workflows you already have configured.
The Alternative I’ve Been Using Since Before WP 7.0
Before WordPress had a native AI Client, there was already a way to connect Claude directly to WordPress: MCP Adapter (the official WordPress.org adapter) + Enable Abilities for MCP (my plugin, which registers abilities in the WP Abilities API).
The architecture is fundamentally different from the native AI Client:
| WP 7.0 Native AI Client | MCP Adapter + Enable Abilities | |
|---|---|---|
| Where the AI lives | Inside the WP admin panel | Claude Desktop / Claude Code |
| Billing | Separate API Key (per token) | Your existing Claude plan |
| Available context | Only what’s in WP | Your full project, files, prior conversations |
| Memory | No | Yes |
| Custom skills / workflows | No | Yes |
| Integration with other tools | No | n8n, Google Drive, terminals, external APIs |
| Granular permission control | Per plugin registering abilities | Per-ability toggle in the admin panel |
With the MCP Adapter, Claude acts on your WordPress from the outside — just like it does with any other tool. That means it has access to its full context: your brand voice, your conversation history, your project files, your automation workflows. WordPress becomes one tool among many, not the environment where the AI lives.
A Concrete Example: Accountants Building Calculators
I have my plugin running in the daily editorial workflow of the team I work with. The users aren’t developers — they’re accountants.
They use it to:
- Create and update posts directly from Claude Desktop, without opening the WP admin panel
- Maintain consistent editorial voice across all articles
- Build HTML accounting calculators (VAT, withholding taxes, salaries) that get inserted as shortcodes
That last one is the part I find most interesting from a practical standpoint. Someone recently told me on LinkedIn that the MCP Adapter is something for “skilled developers.” In practice, the accountants on my team use it to build interactive accounting tools — without writing a single line of code themselves.
The point isn’t that it’s “easy for everyone.” The point is that with Claude’s full context and the plugin’s abilities, non-technical users can do things that previously required a developer.
With WP 7.0’s native AI Client, that workflow doesn’t exist. You’re inside the admin panel, with a chat that only has access to your WordPress, with no project context and no memory of what you did last week.
Being Honest About the Tradeoffs
Not everything favors the MCP Adapter side.
For non-technical users, the initial setup is more complex. You need to install Claude Desktop, configure the MCP Adapter, generate an Application Password, and install the plugin. These are steps that require following a guide.
WordPress 7.0’s native AI Client will eventually be easier to activate for an average user who doesn’t have Claude Desktop and just wants something that works inside their admin panel.
For simple, isolated use cases, the native AI Client may be enough. If you just need “AI to help me draft posts inside WP,” paying for an API Key might be justifiable.
But if you already have Claude Pro, if you use Claude for more than just WordPress, and if you want your AI to have real context about your business — the MCP Adapter is the smarter choice from both an economic and functional standpoint.
Where My Plugin Stands Today
Enable Abilities for MCP is at version 2.0.8. It registers 53 abilities across 11 categories:
- Read and write posts, pages, comments, media, users
- WooCommerce (products, orders, customers)
- The Events Calendar
- Custom Post Types (full CRUD + taxonomies)
- SEO (Rank Math, Yoast, SEOPress)
- Multilanguage (Polylang, WPML)
- Utilities: search-replace, stats, post meta
Each ability is individually toggleable from the admin panel. No bulk activation without control.
It’s free, open source (GPLv2), and published on WordPress.org: