What’s in this article
- What the Abilities API actually is — how your plugins can now talk directly to AI agents.
- Why this matters for agency work — the shift from manual updates to AI-driven site management.
- How to use this for a client site — a practical workflow for automating content and e-commerce tasks.
- How this changes agency services — new ways to scope, price, and deliver WordPress sites.
- My $0.02: A 3-day rollout plan — how to test and implement this on a live site this week.
🚀 Plug this into Claude Code or Claude Desktop
Get the one-click implementation pack. This spec includes a plugin readiness checklist, sample prompts for automating WooCommerce and Rank Math, and a client handoff template for teaching them how to ‘talk’ to their new site.
Want help applying this to your specific client builds? That’s what the Talk-to-Build community is for — a support community for designers and agency owners building with AI.
If you build or run websites on WordPress, your job just changed. On May 20, WordPress 7.0 shipped, and buried in the update was a feature that turns the entire platform into an AI command center.
Until now, AI could help you write a blog post *for* your WordPress site. But it couldn’t log in and publish it. It couldn’t add a new product to your WooCommerce store or update your SEO settings. The AI was a consultant, not an employee. That’s over.
With the new Abilities API and WP AI Client, AI agents like Claude and ChatGPT can now operate your plugins directly. This post breaks down what that means for designers, agency owners, and anyone who wants to stop clicking around the WordPress admin panel and start automating real work.
What actually shipped
WordPress 7.0 introduced two core pieces that work together. First is the Abilities API. Think of it as a universal language for plugins. Any plugin can now declare what it’s able to do. WooCommerce can say, “I can add a product.” Your contact form plugin can say, “I can create a new form.” Rank Math can say, “I can update the SEO title for a post.”
The second piece is the WP AI Client. This is a new, built-in part of WordPress that acts as a switchboard. You connect your preferred AI provider — Anthropic’s Claude, OpenAI’s ChatGPT, Google’s Gemini — and the client lets that AI see all the declared ‘abilities’ from your plugins. When you give the AI a command, the WP AI Client routes it to the right plugin to get the job done.
You don’t need a separate AI plugin for every tool anymore. You don’t need to build a custom integration. You just need WordPress 7.0 and plugins that use the new API. The AI talks to WordPress, and WordPress tells the plugins what to do.
AI Agent (Claude, etc.)
↓
┌───────────────────────────┐
│ WP AI Client │ (The new "phone operator" in WP 7.0)
└────────────┬──────────────┘
↓
┌───────────────────────────┐
│ Abilities API │ (The "phone book" of plugin skills)
└────────────┬──────────────┘
↓
┌────────────┴──────────┬─────────────┬──────────┐
↓ ↓ ↓ ↓
WooCommerce Rank Math Gravity Your Custom
"add_product" "update_seo" "new_form" Plugin...
Before, AI could only give you the instructions. Now, it can pick up the tools and do the work itself.
Why this matters for design and agency work
This isn’t a technical update for developers; it’s an operational shift for everyone who builds and manages websites. The friction of getting things done inside WordPress just dropped dramatically. For a designer, this means less time spent on tedious content entry and more time on actual design work.
For an agency owner, this changes the entire model for site maintenance. The low-value, manual tasks that eat up your team’s time — uploading a batch of blog posts, changing product prices for a sale, updating page meta descriptions — can now be automated with a simple prompt. Your team’s value shifts from doing the clicking to designing the automations.
And for your clients, the business owners, their website stops being a static piece of marketing material they have to pay you to update. It becomes a dynamic tool they can interact with using plain English. This makes the websites you build for them more valuable and useful from day one.
Here’s how I’d actually use this
This isn’t theoretical. You can put this to work on a client project this week. Here is a simple, four-step workflow to automate a common agency task: adding new blog content.
- Connect your AI provider. In the WordPress 7.0 dashboard, there’s a new “AI Connections” settings page. I’d select Claude, paste in my API key, and save. That’s it. The connection is live.
- Verify your key plugins are ready. I’d check that the client’s key plugins, like Rank Math for SEO and maybe Advanced Custom Fields (ACF) for content structure, have been updated to support the Abilities API. Most major plugins have already shipped updates.
- Write a master prompt for content creation. In a Claude Desktop session, I’d craft a prompt that does the whole job in one shot. Something like: “Log into the WordPress site at [URL]. Create a new post titled ‘[Title]’. Use the content from the attached document for the body. Then, use the Rank Math plugin’s ‘update_seo’ ability to set the focus keyword to ‘[Keyword]’ and generate a meta description. Finally, set the featured image using the attached image file.”
- Hand off the prompt, not the login. Instead of teaching the client how to navigate five different screens in the WordPress admin, I’d give them that prompt as a template. Their new workflow is just to fill in the blanks and run it. The AI handles the rest.
This turns a 20-minute manual process into a 2-minute automated one. When you do that across every repetitive task, the time savings for an agency become massive.
What this changes for designer-run agency work
This update creates three immediate shifts in how agencies can price and deliver WordPress projects. It moves you from selling a static object (a finished website) to selling a living system.
Site maintenance retainers become “AI Operator” retainers. Stop selling blocks of hours for manual updates. Instead, sell a retainer for building and managing the AI workflows that run the site. A client isn’t paying for you to upload a blog post; they’re paying for the system that lets *them* upload a blog post by sending an email. It’s a higher-value service.
Plugin choice is now about AI readiness, not just features. When scoping a new project, your first question for any plugin should be, “Does it support the Abilities API?” A plugin that can be automated by an AI is now fundamentally more valuable than one that can’t. This becomes a key part of your recommended tech stack.
Client handoff is now a prompt book, not a video tutorial. The classic 2-hour screen-share walking a client through the WordPress dashboard is dead. The new deliverable is a one-page document with 10-15 plain-English prompts for managing their site. This is faster for you to create and easier for them to use, which means fewer support tickets later.
This is how you build a moat around your agency. You’re not just a designer who can build a pretty site; you’re an operator who can build an intelligent, automated asset for your client’s business.
My $0.02 — How I’d roll this out for a design business
Don’t try to rebuild your whole process overnight. Prove the value with a small, concrete win. Here’s a three-day plan to get this running for your agency or on a client site.
Day 1 — Update and Audit on Staging. Take one client site and clone it to a staging server. Update it to WordPress 7.0. Go to the new AI Connections page and hook up your Claude API key. Then, make a list of the 5 most-used plugins on the site and check their changelogs for “Abilities API support.” Your goal is to have a safe sandbox environment ready to go.
Day 2 — Automate One High-Frequency Task. Pick the single most annoying, repetitive task you do for that client. Maybe it’s adding weekly event listings or updating product inventory from a CSV file. Write a single, detailed prompt in Claude that uses the relevant plugin’s ‘ability’ to perform that task. Run it on the staging site. Tweak it until it works perfectly every time.
Day 3 — Productize the Workflow. Take the prompt from Day 2 and turn it into a service. Document it. Calculate the time it saves. Frame it as a new line item for your maintenance retainers: “Automated Inventory Sync” or “AI-Powered Content Publishing.” Present it to your client not as a technical feature, but as a business solution that saves them time or money. That’s your first sale.
This is exactly how I’m refactoring the maintenance retainers for MK-Way. We’re moving from selling hours to selling automated outcomes. *If you can talk it, you can build it.*
FAQ
Do I need to be a developer to use this?
No. The whole point is to let you control your site with plain English. You need to be able to write a clear instruction, but you don’t need to write any code.
What happens if my favorite plugin doesn’t support the Abilities API yet?
It will continue to work exactly as it did before. You just won’t be able to automate it through the new WP AI Client. The best thing you can do is contact the plugin developer and ask them to add support.
Is it secure to let an AI control my website?
Yes, it’s designed with security in mind. The AI’s actions are limited by the permissions of the WordPress user account you connect it to. For safety, you can start by giving it an ‘Editor’ role instead of a full ‘Administrator’ role.
Can I use this on older versions of WordPress?
No. The Abilities API and WP AI Client are core features of WordPress 7.0 and newer. You’ll need to update your site to use them.
Does this replace page builders like Elementor or Divi?
Not at all. Page builders are for visual design and layout. This new AI functionality is for automating content and data management tasks that happen behind the scenes.
Which AI provider is the best one to connect?
It depends on the task, but I start with Claude for most workflows. Its large context window and ability to follow complex, multi-step instructions make it a great fit for operating a website.
Is there a risk the AI will make a mistake and break my site?
There’s always a risk with automation. That’s why I recommend starting on a staging server first. You can also build confirmation steps into your prompts, like, “Show me a preview of the changes before you publish them.”
Want help applying this?
Four ways to go deeper:
- Build with Builders. Join the Talk-to-Build community to learn how to Earn money with AI, Download our AI Skills, Advance your business, and learn to build real assets — AI-native websites, cinematic AI video, agent-driven workflows — that you can sell to SMBs who want the outcomes but don’t have time to learn the skills.
- 1-on-1 working session. Skip the friction. Book a screen-share with me — bring a real problem, leave with a working piece of it.
- Done-for-you. MK-Way builds AEO-ready websites, apps, and AI agent workflows for design agencies and founders who want it shipped fast.
- Quick question. DM me on Instagram or connect on LinkedIn. I read every message.
This post is part of the AI Pulse atomic series. If you commented “WP7” on one of my videos — this is the breakdown. Sources: seresa.io.
Last updated: May 27, 2026.