An agent can get site info, search the chatbot's knowledge base, list or read stored conversations, and send a chat message to get an AI response.
View Rapls AI Chatbot on WordPress.org
Needs WordPress 6.9 or later for the Abilities API (the plugin itself supports 6.3+) and the plugin active. Every mirrored ability checks manage_options, so only an administrator-level connected user can call any of them.
All five tool registrations (get_site_info, search_knowledge, list_conversations, get_conversation, send_message) are a fixed, literal list in the plugin's MCP server bootstrap, not runtime-dependent, so the set is enumerable and not dynamic.
Grouped by what each one can change. Every one starts off until you enable it.
Returns WordPress site information and the chatbot plugin's configuration, without exposing API keys.
Searches the knowledge base and site content index for matching articles, FAQs and pages.
Lists recent chat conversations with message counts, sorted by creation date.
Returns a conversation's details and full message history by id.
Sends a message to the AI chatbot and returns its response, using the configured AI provider and knowledge base context.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Rapls AI Chatbot 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 Rapls AI Chatbot 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 mirrors its own five-tool MCP registry into the core Abilities API through a dedicated bridge class, so the Bridge can expose all five in addition to the plugin's own MCP endpoint.
Yes, unconditionally, once Rapls AI Chatbot is active. Nothing else has to be configured for the Bridge to discover them.
Needs WordPress 6.9 or later for the Abilities API (the plugin itself supports 6.3+) and the plugin active. Every mirrored ability checks manage_options, so only an administrator-level connected user can call any of 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 Rapls AI Chatbot'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, rapls or Rapls AI Chatbot. 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.