Lets an AI chat widget run a calculator, search the site's posts and pages, fetch basic site information, and submit a visitor's contact request after the visitor explicitly confirms they want it sent.
View Kethu Site Chat Assistant on WordPress.org
Needs WordPress 7.0 or later with the plugin active. None of its six abilities check a WordPress capability: each one is gated only by the plugin's own enabled-tool and agent-ready settings, so any caller the site lets reach them, logged in or not, can use them.
Abilities come from a fixed array of six hardcoded tool classes in tool_instances(); each ability id is built from that class's get_name(), a literal string with no runtime dependency. Not dynamic. These ability names are put together by the plugin's code when it registers them, so we worked them out from that code. Check the exact names on your site's Bridge screen.
Grouped by what each one can change. Every one starts off until you enable it.
Evaluates a math expression for the chat assistant.
Searches the site's content for the chat assistant.
Searches posts for the chat assistant.
Searches pages for the chat assistant.
Returns basic information about the site for the chat assistant.
Submits a visitor's contact request, but only after the visitor has explicitly confirmed in the chat that they want it sent.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Kethu Site Chat 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 Kethu Site Chat 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. It registers six abilities in the core Abilities API with no meta.mcp.public gate, so the Bridge discovers and can wrap all of them once the operator enables the ability's namespace.
Each tool must be individually enabled in the plugin's chat settings. The plugin's own "agent ready" setting must be turned on.
Needs WordPress 7.0 or later with the plugin active. None of its six abilities check a WordPress capability: each one is gated only by the plugin's own enabled-tool and agent-ready settings, so any caller the site lets reach them, logged in or not, can use them.
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 Kethu Site Chat 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, Vivek Kethu or Kethu Site Chat 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.