Turn cache evidence into a deliberate change
When a WordPress site needs Cloudflare cache work, follow the evidence from the connected site to the scope you intend to change.
1
Connect the WordPress capability
Use WordPress 6.9 or newer with PHP 8.0 or newer. Install and activate the WordPress MCP Adapter, then install and activate MCP Abilities – Cloudflare. The WordPress user must have the manage_options capability. Configure Cloudflare credentials in the standard WordPress options or supported Cloudflare constants before direct API work. If the credentials are missing, the operation stops with an explicit configuration error.
2
Inspect the connected state
Use the Cloudflare checks to inspect the connected zone, cache settings, Development Mode, and cache rulesets. For a specific public URL, test its cache status and read cf-cache-status, cache-control, age, set-cookie, and related headers. The result shows what the edge is serving before you choose a cache operation.
3
Match the scope to the change
Choose the scope that matches the change: all cache, selected URLs, a URL prefix, tags, or hosts. Selected URL lists, cache tags, and hostnames support up to 100 entries where that scope is available; tags require a supported Cloudflare plan. Use a URL-prefix purge for cached HTML when an exact URL purge does not evict the edge object.
4
Apply the bounded change
Read Development Mode, or deliberately enable or disable it when the work requires that change. The managed anonymous WordPress HTML cache rule starts as a dry run; when you ensure it, it 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, giving you a receipt to verify.
Choose the control by the object you need to change
Each control keeps the purge scope and its evidence visible, so the requested change can be checked against the affected object.
Inspect the connected state
Check the connected zone, cache settings, Development Mode, and cache rulesets. Test a public URL when you need cache-status headers such as cf-cache-status, cache-control, age, or set-cookie before acting.
Clear all cache
Use the all-cache scope when the change must remove every cached object covered by the operation.
Clear selected URLs
Use up to 100 selected URLs when only named public resources need clearing.
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.
Read the purge receipt
A successful purge response includes the purge type, payload keys, Cloudflare purge ID, and authentication mode. Cloudflare work requires configured credentials and the manage_options capability.
The runtime that exposes the WordPress abilities
These named components provide the registration and MCP connection this plugin needs.
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 connection for focused cache control
Download the stable self-hosted MCP Abilities – Cloudflare ZIP to obtain the WordPress plugin that lets an AI client inspect Cloudflare state and apply focused cache control. Use the scope and receipt details above to make the first change deliberate and verifiable.