There is a meaningful difference between an AI that writes a draft you paste in, and an AI that connects to your site and makes the change itself. WordPress crossed that line. The Abilities API in core, combined with the MCP Adapter introduced on the WordPress developer blog in February 2026, means tools like Claude and Cursor can read from and write to a WordPress site directly.
This is genuinely useful and it is genuinely a new category of access. Both things are true.
The question is not whether an AI agent can change your site. It now can. The question is what you have decided it is allowed to change, and whether you would notice if something went wrong.
Primo Collab
What the Abilities API actually is
Think of it as a menu. Rather than an AI tool poking at your database or guessing at REST endpoints, WordPress publishes a structured list of things that can be done on the site, and each of those is an “ability.” An agent asks for an ability by name, and WordPress runs its own code to perform it, with the normal validation and hooks that a plugin or theme expects.
That last part matters more than it sounds. It is the difference between an agent editing your site the way a careful developer would, and an agent writing directly to the database and leaving your caches, validation, and plugin logic out of the loop.
The MCP Adapter is the layer that exposes those abilities to AI assistants in a format they can use.
What this unlocks in practice
The realistic wins are the repetitive, high-volume, low-judgment jobs that nobody enjoys:
- Generating and applying alt text across a media library with hundreds of images.
- Bulk-updating product descriptions or metadata to a consistent format.
- Finding and flagging broken internal links.
- Drafting and staging routine content for review.
- Auditing pages against a checklist and reporting what fails.
These are exactly the tasks where a person gets bored on item forty and starts making mistakes, and where an agent working from a defined ability list does not.
Scope the access like you would for a contractor
An agent connected to your site through this path is not a suggestion engine. It is an operator, and it deserves the same access decisions you would make before handing a new contractor an admin login. We covered those guardrails in detail in AI Agents That Edit Your Website Directly: How the Guardrails Actually Work. The short version: staging before production, the narrowest ability set that gets the job done, a human confirming anything irreversible, and a log you actually read.
What this does not mean
It does not mean your site is now exposed by default. Nothing connects until an administrator authenticates a provider and grants access. The risk here is not that WordPress opened a door. It is that the door is now easy enough to open that it can get opened casually.
The mistake to avoid
Granting broad access because scoping it properly feels like friction, and reviewing every change feels slow. That trade looks fine for weeks and then costs a great deal the first time an agent does exactly what it was asked to do on the wrong set of pages. Scoped permissions and a staging step cost an afternoon to set up. The alternative costs a lot more once, at a time you did not choose.