Choose the change from what the edge is serving
A cache fix is easier to trust when the affected object and the evidence for the response are clear before a change is sent.
1
Prepare the WordPress connection
Run WordPress 6.9 or newer with PHP 8.0 or newer. Install and activate the WordPress MCP Adapter and MCP Abilities – Cloudflare, then give the WordPress user the manage_options capability. Configure Cloudflare credentials in standard WordPress options or supported Cloudflare constants. Missing credentials stop remote work with an explicit configuration error.
2
Establish the control surface
Use cloudflare/get-zone, cloudflare/get-cache-settings, and cloudflare/get-cache-rulesets to establish the connected zone, cache settings, and rulesets that govern the decision.
3
Match the scope to the affected objects
Use cloudflare/clear-cache after the evidence identifies the cache object. Choose the scope that fits the requested result instead of clearing more than necessary.
4
Apply the guarded operation
The cloudflare/ensure-wordpress-html-cache-rule ability starts as a dry run, targets only anonymous public WordPress HTML requests, and preserves existing Cloudflare rules. A successful purge returns the purge type, payload keys, Cloudflare purge ID, and authentication mode.
Use the control that matches the question
Separate the diagnostic checks, mode control, and purge scopes before you send a request.
Test the public response
Use cloudflare/test-url-cache-status for one public URL to see the edge response before a purge. It returns cf-cache-status, cache-control, age, set-cookie, and related headers.
Read or change Development Mode
Use cloudflare/get-development-mode to read the current mode. Use cloudflare/set-development-mode only for a deliberate enable or disable when the work calls for it.
Clear all cache
Use the all-cache scope when the change must remove every cached object covered by the operation.
Clear selected URLs
Choose up to 100 explicit URLs for a narrow purge of specific resources.
Clear a URL prefix
Use a URL-prefix purge for cached HTML when an exact URL purge does not evict the edge object.
Clear tags or hosts
Use up to 100 cache tags on supported Cloudflare plans or up to 100 hostnames when the affected objects are identified by those groups.
What the plugin needs to run
Each row names one required component, its constraint, and its role.
WordPress 6.9 or newer
WordPress Abilities APIProvides the native ability registration layer used by the add-on.
PHP 8.0 or newer
PHP 8.0Provides the required server runtime for the plugin.
Installed and active
WordPress MCP AdapterExposes the registered WordPress abilities to MCP clients.
Download the WordPress cache control
Download the stable self-hosted MCP Abilities – Cloudflare ZIP for the WordPress site where an AI client will inspect Cloudflare state and apply a focused cache change.