SpeedyCache
ConditionalOnce enabled, an agent can read the site's caching, file optimization, and CDN configuration, check cache and preload status, and clear or rebuild the cache.
An AI agent can count how many post revisions a site stores and estimate their size, list them a page at a time, delete a bounded batch of revisions for a given scope, and run OPTIMIZE TABLE on the posts and postmeta tables afterward.
View Revision Autopilot on WordPress.org
Needs WordPress 6.9 or later for the Abilities API. Counting and listing revisions need edit_posts by default, and deleting revisions or optimizing tables need manage_options by default; both are filterable by the site.
Grouped by what each one can change. Every one starts off until you enable it.
Returns how many post revisions the site stores and an estimate of their size, by post type.
Returns one page of stored revisions with their parent post and estimated size.
Permanently deletes a bounded batch of revisions for a scope; not reversible.
Runs OPTIMIZE TABLE on the posts and postmeta tables to reclaim space.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Revision Autopilot 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 Revision Autopilot 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 four abilities register unconditionally with explicit readonly/destructive annotations and their own permission callback, so the Bridge can wrap and expose them directly.
Yes, unconditionally, once Revision Autopilot is active. Nothing else has to be configured for the Bridge to discover them.
Needs WordPress 6.9 or later for the Abilities API. Counting and listing revisions need edit_posts by default, and deleting revisions or optimizing tables need manage_options by default; both are filterable by the site.
Once enabled, an agent can read the site's caching, file optimization, and CDN configuration, check cache and preload status, and clear or rebuild the cache.
An agent can list and filter Boost's performance modules, toggle a single module on or off, read the latest mobile and desktop speed score, and clear the page cache.
An agent can force every visitor's browser to fetch fresh CSS, JS, and images after a site change, optionally purging the page cache too, and can read back the plugin's current cache-busting configuration and status.
Verified from Revision Autopilot'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, Takahiro Nishii or Revision Autopilot. 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.