An agent can send a single message to the site's configured AI chatbot and get back the assistant's reply, using the chatbot's own system instruction or an override supplied in the call.
View Chagency on WordPress.org
Needs WordPress 7.0 or newer (the plugin's own stated minimum) and PHP 7.4 or newer, with the Chagency plugin active and its AI provider configured. The single ability requires manage_options, so only an administrator-level connected user can call it.
Grouped by what each one can change. Every one starts off until you enable it.
Sends a message to the site's configured AI provider using the chatbot's system instruction and returns the reply.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Chagency 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 Chagency 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. It registers one ability, chagency/send-message, in the core Abilities API with meta.public true, so the Bridge discovers it (it does not need that flag to do so) and can expose it once enabled.
Yes, unconditionally, once Chagency is active. Nothing else has to be configured for the Bridge to discover them.
Needs WordPress 7.0 or newer (the plugin's own stated minimum) and PHP 7.4 or newer, with the Chagency plugin active and its AI provider configured. The single ability requires manage_options, so only an administrator-level connected user can call it.
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 Chagency'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, Jordy Meow or Chagency. 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.