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.
The AI plugin must be installed and active on WordPress 6.9 or newer (its own readme lists 7.0 as its floor). Reading settings needs manage_options; reading content and most content-generation abilities check edit_post on the specific post (or edit_posts generally); reading users mostly needs no special capability unless filtering by role (list_users); comment abilities need moderate_comments; image abilities need upload_files.
Matches easymcpai's listed count of 22. All 22 ids are literal returns from get_id()/sprintf() calls or literal string arguments, not runtime-computed, so the set is fixed, not dynamic. None of the 17 experiment abilities or the 2 ai/get-post-* abilities declare a meta.annotations array at all (Abstract_Ability::meta() only returns show_in_rest), so per the Bridge's fail-safe rule all 19 are destructive risk regardless of what they actually do; only the 3 core/* abilities (polyfilled from WordPress core's own ability classes) declare explicit readonly annotations.
Grouped by what each one can change. Every one starts off until you enable it.
Reads posts of types exposed to abilities, by ID, by slug, or as a filtered query.
Returns WordPress settings exposed to abilities as a flat map of setting name to value.
Looks up one or more readable WordPress users by ID, email, username, or slug, or a filtered query.
Returns a post's content, title, slug, author, type, and excerpt by post ID.
Returns the taxonomy terms attached to a post, optionally filtered by taxonomy.
Generates a suggested excerpt from a post's content or supplied text.
Generates an SEO meta description suggestion and can hand it to a connected SEO plugin.
Applies previously suggested editorial notes to a post's content.
Shortens, expands, or rephrases a passage of block content.
Generates a suggested URL slug from a post's title or content.
Generates ghost-text continuation suggestions while writing a paragraph.
Generates a suggested post title from its content.
Adds block-by-block editorial suggestions covering accessibility, readability, grammar, and SEO.
Generates accessible alt text for an image using a vision model.
Summarizes long-form content into a shorter overview.
Scores a comment for toxicity and sentiment to help moderation decisions.
Suggests tags and categories for a post based on its content.
Translates paragraph and heading blocks into a different language.
Generates a new image or edits an existing one from a text prompt.
Imports a base64-encoded image into the media library.
Generates an image-generation prompt from post content.
Generates a suggested reply to a comment for a moderator to review.
No abilities match that search.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. AI 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 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.
Conditionally. The official AI plugin registers 22 real abilities (17 experiment abilities, 2 post-lookup abilities, and 3 core/* abilities it polyfills), but every one of them is gated behind its own feature toggle, all off by default, so none register until an operator turns on both the plugin's global AI-features switch and that specific feature.
A global 'AI features enabled' option must be on (defaults to off); with it off, nothing in the plugin registers any ability.. Each of the 17 experiment abilities (excerpt-generation, title-generation, slug-generation, etc.) is its own separate Feature with its own per-feature option, also off by default; both the global switch and that specific feature's switch must be on for its ability to register.. core/read-content, core/read-settings, core/read-users, ai/get-post-details, and ai/get-post-terms are grouped behind one additional 'Custom Abilities' feature toggle, itself off by default alongside the same global switch.. Most of the content-generation abilities also need an AI connector plugin configured with a text or image generation model; the ability can register without one but calling it will fail..
The AI plugin must be installed and active on WordPress 6.9 or newer (its own readme lists 7.0 as its floor). Reading settings needs manage_options; reading content and most content-generation abilities check edit_post on the specific post (or edit_posts generally); reading users mostly needs no special capability unless filtering by role (list_users); comment abilities need moderate_comments; image abilities need upload_files.
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.
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.
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 AI'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, WordPress.org or AI. 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.