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.
View AI Block Editor on WordPress.org
The Abilities API needs WordPress 6.9+; no other WordPress version floor is set by the plugin itself. The ability checks the edit_posts capability, granted to contributors and above, with no per-post ownership check beyond that.
Grouped by what each one can change. Every one starts off until you enable it.
Returns titles, excerpts, content and links for posts, pages and public custom post types, by ID, type or search term.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. AI Block Editor 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 AI Block Editor 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 plugin's AIEditor_Post_Abilities class registers one fixed ability, ai-editor/query-content, on the WordPress Abilities API init hook whenever the Abilities API classes exist.
The WordPress Abilities API (WP_Ability class and wp_register_ability) must exist.
The Abilities API needs WordPress 6.9+; no other WordPress version floor is set by the plugin itself. The ability checks the edit_posts capability, granted to contributors and above, with no per-post ownership check beyond that.
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 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.
Verified from AI Block Editor'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, Virgildia or AI Block Editor. 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.