A brief becomes a real page.LiteSpeed Cache MCP integration
Clear the cached page right after the AI changes it.
EMCP reads whether LiteSpeed Cache is on, how long pages stay cached and whether this server can actually purge. After a change it asks LiteSpeed Cache to purge one path, with its query variants, or the whole page cache. Where a purge cannot work, EMCP refuses instead of reporting success.
Free integrationLiteSpeed Cache 7.9.2 on a LiteSpeed server
One edit, one purge
| Step | What EMCP does |
|---|---|
| 01 · Status | Cache on, purge supported |
| 02 · Purge | /contact/ and its query variants |
| 03 · History | Purge recorded, not undoable |
| 04 · Check | Miss, then hit with new content |
A practical place to start
From an edited page to a fresh copy for visitors.
- 01
Check support
status reports the cache and minification flags, the cache lifetimes, the server type and whether purges are supported on this connection.
- 02
Purge the page
purge-path takes one site-relative path and purges it with its query variants. purge-page-cache clears the whole page cache.
- 03
Confirm it
Load the page and check LiteSpeed's cache response header: a miss, then a hit again, means visitors now get the new version.
Built for LiteSpeed Cache
What the cache is doing
status reads LiteSpeed Cache’s own configuration fresh on every call: whether the page cache is on, CSS, JavaScript and HTML minification, and the public, private and front page lifetimes. It also reports the server type and whether purges are supported on this connection, so your AI knows before it tries.
Purges that really happen
LiteSpeed Cache purges by sending instructions to the LiteSpeed web server in the response headers. EMCP sends a purge only on an HTTP request to a supported LiteSpeed server with the cache on, and refuses otherwise. It still cannot see the server’s cache, so it asks you to confirm with the next cache response.
Narrow by default
purge-path takes one path on this site and nothing else: no other origin, query string, fragment or traversal. purge-page-cache clears every cached page and needs confirmation like every write. Every purge is in History in EMCP Tools or EMCP Lite.
Use the LiteSpeed Cache tool reference for operation names and arguments, and Wordfence for the security side of the same site.
Get connected
Put LiteSpeed Cache in your AI’s toolkit.
- 1
Install LiteSpeed Cache
Install EMCP Tools 3.21.1 or later, or EMCP Lite 1.0.5 from WordPress.org, with LiteSpeed Cache 7.9.2 on a single site. Other versions and multisite are refused.
- 2
Connect over HTTP
Purges need an HTTP connection (OAuth or an application password) to OpenLiteSpeed, LiteSpeed Enterprise or LiteSpeed ADC with the cache on. A WP-CLI connection can read status only.
- 3
Enable the write tool
litespeed-read is on; litespeed-write starts disabled. Enable it under EMCP Tools > Tools > Plugins > LiteSpeed Cache and reconnect your AI client.
Then connect Claude Code, Claude Desktop, or Cursor to use the LiteSpeed Cache tools enabled on your site. Compare Free and Pro access.
A few useful details
Before you connect.
Questions about LiteSpeed Cache, supported operations, and the workflow on your site.
Why does it refuse on my server?
Only a LiteSpeed web server can act on LiteSpeed's purge instructions. On Apache or Nginx, or over WP-CLI, a purge would report success without clearing anything, so EMCP refuses.
Does purging a path include query strings?
Yes. LiteSpeed Cache purges the path and its query variants, such as ?ref=newsletter.
Can it change cache lifetimes?
No. It reads the public, private and front page lifetimes but never changes settings.
Can I undo a purge?
No. Cached copies cannot be put back; the cache refills as visitors load pages.
Your tools. Your WordPress site.