Get the plugin
WP MCP/Integrations/Operations

Operations integration

W3 Total Cache MCP

get-w3tc-status on the theme dispatcher pair reads W3 Total Cache's config through its public w3tc_config() API, one allowlisted key at a time: whether the page, database, object, minify, browser, CDN and Varnish caches are enabled, and with which engine. Server lists, passwords and CDN keys are never read. purge-w3tc-cache empties every cache through the plugin's own purge-all. Like any cache purge it is not a content write, so it is not snapshotted and is not undoable: the response says recoverable:false, and it needs confirm:true and manage_options.

theme-readtheme-write

What your AI can do

Real W3 Total Cache operations, every write reversible.

  • See which W3 Total Cache caches are enabled and their engines
  • Purge every cache after a content or design change (confirm:true)

Example prompts

Example W3 Total Cache prompts.

Is page caching on, and is it using disk or Redis?

Purge W3 Total Cache now that the new homepage is live.

Under the hood

The W3 Total Cache calls, under the hood.

wpmcp, w3-total-cache

theme-read({ operation: "get-w3tc-status" })

theme-write({ operation: "purge-w3tc-cache", confirm: true }), not undoable; recoverable:false

In the free plugin

The W3 Total Cache integration is in the free plugin.

The core W3 Total Cache tools ship in the free, GPL plugin with the full snapshot and undo engine, and no trial clock. Pro adds 133 more tools, including Elementor deep editing, the other page builders, the forms adapter pack and, for some integrations, extra operations. The pricing page lists what each tier includes.

Frequently asked

W3 Total Cache MCP: questions, answered.

Can I undo a purge?

No. A purge empties caches that rebuild themselves; there is no before-image worth restoring, so it is not snapshotted and the response says so. That is why it needs confirm:true.

Point your AI at W3 Total Cache.