An AI agent can create a new AutomatorWP automation, add triggers or actions to an existing one, and run or execute an automation's actions immediately, using AutomatorWP's own no-code automation builder.
View AutomatorWP on WordPress.org
AutomatorWP needs to be installed and active on WordPress 6.9 or later for these abilities to register; they load with the plugin's bundled AI Assistant module and are not behind a separate toggle. All four abilities check the manage_options capability.
Grouped by what each one can change. Every one starts off until you enable it.
Creates a new automation in AutomatorWP.
Adds one or more triggers to an existing automation.
Adds one or more actions to an existing automation.
Runs or executes an automation's actions immediately, without waiting for its trigger.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. AutomatorWP registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from AutomatorWP starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Yes. The bundled AI Assistant module registers four abilities with wp_register_ability under the automatorwp namespace unconditionally when the plugin loads, so any of them can be switched on by the site operator.
Yes, unconditionally, once AutomatorWP is active. Nothing else has to be configured for the Bridge to discover them.
AutomatorWP needs to be installed and active on WordPress 6.9 or later for these abilities to register; they load with the plugin's bundled AI Assistant module and are not behind a separate toggle. All four abilities check the manage_options capability.
An agent can read OttoKit's SaaS connection status, access-control settings, system health (cron jobs, database table, webhook log counts), configured automation triggers, which supported integrations are active, and paginated webhook execution logs.
Once an operator turns on the relevant feature toggles, an agent can read a site's exposed settings, users, and post content and terms, and can ask the plugin's AI experiments to draft or suggest excerpts, titles, slugs, meta descriptions, editorial notes and updates, summaries, translations, classifications, type-ahead text, image alt text, generated images, and comment moderation or reply suggestions, though running the content-generation ones also needs an AI connector configured.
An agent can query posts, pages and other public post types by ID, type or search term, returning titles, links, excerpts, or the content converted to Markdown.
Verified from AutomatorWP's own free wordpress.org code on 28 September 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, Ruben Garcia or AutomatorWP. Back to the full directory.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.