An AI chat assistant can look up the list of internal support documents and read one in full to answer a visitor's question, and can send an email to site staff with a visitor's message and reply address when it cannot answer.
View Satollo Assistant on WordPress.org
Needs WordPress 7.1 or later per the plugin's own listing (the Abilities API itself needs 6.9+). None of its abilities check any WordPress capability at all, their permission_callback returns true unconditionally, so any connected user, including a logged-out one, can call them once enabled.
Not listed in the easymcp index. None of the three declare meta.annotations, so the Bridge's fail-safe rule classifies all of them as destructive even though two are reads.
Grouped by what each one can change. Every one starts off until you enable it.
Emails the site staff with a visitor's message and reply address.
Lists the titles and excerpts of the plugin's private support documents.
Returns the full content of one private support document by its post ID.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Satollo 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 Satollo 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. All three abilities register unconditionally with an execute callback and a permission callback, so the Bridge can wrap and expose them as soon as it discovers them.
Yes, unconditionally, once Satollo Assistant is active. Nothing else has to be configured for the Bridge to discover them.
Needs WordPress 7.1 or later per the plugin's own listing (the Abilities API itself needs 6.9+). None of its abilities check any WordPress capability at all, their permission_callback returns true unconditionally, so any connected user, including a logged-out one, can call them once enabled.
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 Satollo 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, Stefano Lissa or Satollo 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.