An AI agent can read and manage posts, pages, terms, media, users and plugins, browse and propose edits to theme or plugin files under wp-content, save and recall a private per-user memory, run web or image search, make outbound HTTP calls, and call any REST route on the site, each gated by its own WordPress capability and by settings the site operator turns on.
View MAIA, Multipurpose AI Assistant on WordPress.org
Needs WordPress 6.9 or later for the Abilities API and an AI connector configured for MAIA to do anything. Content abilities need edit_posts or a per-post-type capability checked further at execution, file abilities need edit_themes, plugin management needs activate_plugins, and the generic REST call ability needs manage_options.
22 abilities register unconditionally; the other 12 (search, HTTP, memory, generic REST, image generation) register only when their setting or a connector is configured, so the live count varies per site. Not listed in the easymcp index.
Grouped by what each one can change. Every one starts off until you enable it.
Asks the user to choose between concrete alternatives instead of listing the options as plain text.
Lists the REST API namespaces registered on this site.
Finds files under wp-content by a name glob pattern such as *.php.
Gets the full content of a single post, page, or other REST-exposed post type by ID.
Gets information about this WordPress site including active theme, plugins, and WordPress and PHP versions.
Searches file contents under wp-content for a plain-text string or a regular expression.
Makes a GET or HEAD HTTP request to any external URL.
Searches the web for images using the configured search provider, returning image URLs and source pages without saving anything.
Lists posts, pages, or another REST-exposed post type such as WooCommerce products.
Lists files and subdirectories inside wp-content, excluding themes, plugins and uploads paths outside the jail.
Lists the files of a plugin or theme that the edit-file ability is allowed to modify.
Lists media library items such as images and documents.
Lists installed plugins with name, file path, version and active status, or details for one plugin.
Lists post types that can be managed through the content abilities.
Lists taxonomy terms such as categories, tags, or a custom taxonomy.
Lists users of the site with id, name and roles.
Lists this user's saved memory keys, newest first, without their content.
Loads the full content of a previously saved memory by its key or id.
Saves a fact worth remembering about the user for future conversations under a short key, overwriting any existing key.
Searches this user's saved memories by keyword.
Reads a text file under wp-content, windowed by line range.
Searches the titles and message content of this user's earlier conversations with MAIA.
Displays an image to the user in a card with buttons to save it to the media library or insert it into content.
Searches the web using the site's configured search provider for current information outside the site's own content.
Creates a new post, page, or other REST-exposed post type, defaulting to draft status.
Generates an image from a text prompt using AI and saves it directly to the media library.
Calls any REST API route registered on this WordPress site directly, including core, WooCommerce, or any other plugin's routes.
Deletes a post, page, or other REST-exposed post type by ID, moving it to Trash by default.
Proposes an edit to a plugin or theme file as a diff pending user confirmation; it does not write by itself.
Makes a POST, PUT, PATCH or DELETE HTTP request to any external URL.
Installs, activates, deactivates, or deletes a plugin.
Creates, updates, or deletes a taxonomy term such as a category or tag.
Deletes a saved memory by key or id.
Updates an existing post, page, or other REST-exposed post type by ID, changing only the fields provided.
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. MAIA, Multipurpose AI Assistant 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 MAIA, Multipurpose AI Assistant 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. Every ability registers into the core Abilities API on wp_abilities_api_init with a real execute and permission callback, so whichever ones a site operator has enabled are directly bridgeable.
Web and image search abilities only register if a search provider (Brave Search or Tavily) is configured. HTTP fetch/request abilities only register if MAIA's HTTP tools setting is enabled. The five memory abilities only register if MAIA's memory setting is enabled. The generic REST discovery and call abilities only register if MAIA's full REST access setting is enabled. The image-generation ability only registers if a configured AI connector supports image generation. Even once registered, a non-readonly ability also needs MAIA's own write tools setting enabled, and a file ability needs its file tools setting enabled, or the permission check still fails.
Needs WordPress 6.9 or later for the Abilities API and an AI connector configured for MAIA to do anything. Content abilities need edit_posts or a per-post-type capability checked further at execution, file abilities need edit_themes, plugin management needs activate_plugins, and the generic REST call ability needs manage_options.
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 MAIA, Multipurpose AI Assistant'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, Avram or MAIA, Multipurpose AI Assistant. 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.