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 agent can read the page cache policy (enabled state, TTLs, excluded URLs and cookies), cache and Cloudflare connection health, and preloader state, and run a cache test. It can change cache policy settings, purge the whole cache or a list of URLs, posts or tags, and start a preloader.
View Super Page Cache on WordPress.org
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 6.5), plus PHP 7.4 or later and the plugin active. The abilities check the capability manage_options.
Counted from the plugin code on 10 November 2026; settings or feature flags that the count does not evaluate may hide some of these abilities.
Grouped by what each one can change. Every one starts off until you enable it.
Destructive also covers abilities the plugin does not declare read-only: the Bridge treats a missing annotation as destructive until the owner reviews it, so some of them may only look things up.
Returns the effective page cache policy: enabled state, TTLs, excluded URLs and cookies, and the bypass rules. Lists the fields locked by wp-config.php constants.
Runs the plugin cache test against its static test page and reports the Cloudflare and disk cache results. The tested URL is fixed by the plugin.
Returns the preloader state and the cache and Cloudflare connection health. Pass the job_id returned by spc/start-preload to follow that preload run.
Updates page cache policy fields (enabled state, TTLs in seconds, excluded URLs and cookies, bypass rules). Only the provided fields change; list fields are replaced as a whole. Some fields purge the whole cache and re-sync the Cloudflare cache rule when changed.
Purges the whole cache, a list of site URLs, posts (with their related archive URLs) or cache tags. Purging by tags requires Super Page Cache Pro with Cache Tags enabled.
Starts the cache preloader for the configured sources (menus, sitemaps, latest posts), or for a given list of site URLs. Only one preload can run at a time. The preload runs in the background; pass the returned job_id to spc/get-status to follow it.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Super Page Cache registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Plugins’ own tools" in the admin, "Other plugins" before 1.12.0). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from Super Page Cache 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. Super Page Cache calls wp_register_ability() for 6 abilities in its current code on wordpress.org, so the Bridge can discover them once the plugin is active.
Yes, once Super Page Cache is active, as far as its code shows. This directory reads the code but does not evaluate every setting or feature flag, so check the plugin's own settings if an ability is missing on your site.
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 6.5), plus PHP 7.4 or later and the plugin active. The abilities check the capability manage_options.
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 read Optimole image delivery settings and offload progress, change quality, resize, lazy loading and exclusion rules, move selected media library images to Optimole Cloud and back, and clear cached image variants.
Verified from Super Page Cache's own free wordpress.org code (version 5.3.10) on 10 November 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, Optimole or Super Page Cache. 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.