MCP Abilities – Cache Enabler: Keep Cache Changes Proportional to the Problem
When a WordPress page is stale, MCP Abilities – Cache Enabler gives an authenticated MCP workflow a precise cache target. It avoids a blind site-wide purge.
The cache operations you can call
The authenticated MCP surface covers inspection, diagnosis, configuration, scope-specific clearing, and bounded recovery.
Inspect state and settings
Read Cache Enabler status and settings before changing anything, so the current cache condition is visible.
Diagnose a page and list cached URLs
For a page-specific question, diagnose the page; for cache inventory, list cached URLs to see which locations are present.
Update settings or plugin state
Update Cache Enabler settings or explicitly enable or disable the plugin when its configuration or runtime state must change.
Purge one target
Purge a single URL or post when the stale result is confined to that target.
Purge a broader scope
Purge expired cache, the current site, or the complete cache when the evidence calls for a wider clearing boundary.
Refresh or remove the cache directory
Refresh the backend for bounded recovery; delete the cache directory only as an emergency, with its path guard and explicit confirmation.
Choose the smallest change that resolves the evidence
Use this sequence to match the cache change to the evidence. Avoid a broad purge and confirm that WordPress serves the expected result.
Inspect the condition
Read status and settings; use page diagnosis or cached-URL listing when the question is scoped to a page or the cache inventory.
Choose the boundary
Select URL, post, expired cache, site, or complete cache according to the problem you found.
Make the change
Use the matching purge, settings, enable-or-disable, or backend-refresh operation. Keep directory deletion for an emergency that satisfies its path guard and confirmation requirement.
Verify the result
Check Cache Enabler through WordPress after the change. If the result is still wrong, the evidence shows whether another bounded operation is needed.
What this workflow requires
The documented operations rely on the 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.
Put the documented cache controls within reach
Download the MCP Abilities – Cache Enabler package when WordPress needs authenticated MCP access. Inspect Cache Enabler and clear stale pages with a justified scope. Once the required components are active, the package exposes those controls through WordPress.