WordPress 7.0 introduces the Abilities API and an official MCP Adapter, a standard way for a site to publish capabilities that outside AI agents can discover and call. This plugin can use that surface to expose your workflows as agent-invokable tools, so an assistant like Claude or ChatGPT can list your workflows and run one on request.
This is an advanced, opt-in feature. It is off by default, and turning it on never changes how your workflows run for normal use.
What you need
- A WordPress build that ships the Abilities API (WordPress 6.9 or 7.0 and later). The plugin detects it automatically. On older WordPress the toggle has no effect.
- For connections over MCP, the free MCP Adapter plugin. Without it, your abilities are still reachable through the core Abilities REST endpoint.
Turn it on
- Open Settings > AI Agents (MCP).
- Switch on Expose workflows to AI agents. It is off by default.
- The panel then shows which workflows are exposed and the endpoints an agent client connects to.
Which workflows are exposed
Only active workflows whose trigger is manual or webhook are exposed, up to a limit of 100. A read-only discovery ability, wp-ai-workflows/list-workflows, is also published so an agent can see what is available. Each exposed workflow gets its own runnable ability named wp-ai-workflows/run-<id>.
The input an agent supplies depends on the trigger:
- Manual trigger: a single optional text input that overrides the workflow’s stored trigger content for that run.
- Webhook trigger: a payload whose fields match the keys you defined on the webhook trigger.
Connect an agent
The settings panel gives you two things to copy:
- The MCP endpoint URL, shown when the MCP Adapter is active. Point your agent client at this to connect over MCP.
- The Abilities REST endpoint, the core list endpoint the adapter reads from. Use this if you are working with the Abilities API directly.
How runs are handled
Exposed workflows run locally on your site using your own AI provider keys, the same as a normal local run. Every call still respects your per-workflow spend controls and budgets, so agent-driven runs cannot bypass the limits you set. See Local vs Cloud execution.
Who can invoke a workflow
By default only administrators can run an exposed workflow, and the toggle is off until you deliberately enable it. The required capability is filterable for developers who need to widen or tighten access, but the safe default is administrator only.