WordPress now has official building blocks for AI-aware plugins and agent workflows: the Abilities API, WordPress AI Client and MCP Adapter. Here is how the pieces fit together.
Abilities are the foundation
The Abilities API gives WordPress functionality a standardized, typed and permission-aware way to describe what it can do. WordPress 7.1 expands discovery, public exposure and client compatibility.
The AI Client handles model access
The WordPress AI Client is designed as a provider-agnostic PHP layer, so plugin code can interact with an available AI provider without hard-wiring the application logic to one model vendor.
MCP opens an agent-facing door
The official MCP Adapter can expose selected WordPress abilities as MCP tools. That allows compatible AI clients to discover and execute approved site capabilities instead of relying on brittle browser automation.
Permissions still matter
Agent access is not a reason to make everything public. Abilities should have explicit permission callbacks, narrow inputs and outputs, and a deliberate exposure policy. Read-only workflows are a sensible place to start.
Where custom development becomes useful
The opportunity is not “add AI” as a feature label. It is mapping a real workflow—content operations, reporting, catalog work, support or administration—into abilities that can be tested, audited and safely reused.
Tell us what you are trying to achieve. We’ll tell you what the WordPress work actually involves.
Start a project →