The cache operations you can call
The authenticated MCP surface groups the documented operations by the decision they support.
Inspect state and settings
The registered inspection surface covers Cache Enabler state and settings, so an operator can understand the current cache situation before choosing an intervention.
Diagnose a page and list cached URLs
The product includes operations for diagnosing a page and listing cached URLs when the question is page-specific or concerns the cache inventory.
Change settings or plugin state
The documented surface includes operations for updating Cache Enabler settings and explicitly enabling or disabling the plugin.
Purge one target
Use the scoped clearing operations for a URL or a post when the stale result is limited to one target.
Purge a broader scope
Broader clearing operations cover expired cache, the current site, and the complete Cache Enabler cache.
Refresh or remove the cache directory
The documented surface includes backend refresh and emergency cache-directory deletion. Directory deletion is path guarded and requires explicit confirmation.
Use the narrowest operation that fits
This is an operator practice for choosing among discrete authenticated MCP operations; it does not claim that the add-on owns the whole sequence.
01
Inspect
Begin with the registered state and settings operations. Use page diagnosis or cached-URL listing when the question concerns a page or the cache inventory.
02
Choose scope
Match the operation to the desired clearing scope: a URL, a post, expired cache, the site, or the complete cache.
03
Act
Use the relevant purge, settings, enable-or-disable, or backend-refresh operation. Reserve cache-directory deletion for an emergency that meets its path guard and explicit-confirmation requirement.
04
Verify
The product’s stated purpose is to let an authenticated MCP workflow inspect Cache Enabler state, clear stale cached pages, and verify cache behavior through WordPress. Use what you learn to decide whether another bounded operation is needed.
What this workflow requires
The documented operations rely on the source-owned runtime and components that register, supply, and expose the typed cache controls.
Required through WordPress 6.9 or newer.
WordPress Abilities APIRegisters the typed cache operations used by this add-on.
Required server runtime.
PHP 8.0 or newerProvides the PHP runtime required by the add-on.
Required
Cache EnablerProvides the cache state and purge mechanisms this add-on diagnoses and controls.
Required
WordPress MCP AdapterExposes registered WordPress abilities through Model Context Protocol.
Required
MCP Expose AbilitiesSupplies the controlled public ability surface used by this add-on.
Make the documented cache operations available
If your WordPress workflow uses Cache Enabler and needs inspectable cache management through MCP, download the package and make the documented surface available to your operators. Start with state and page diagnosis, then use the narrowest action that resolves the evidence you find.