Breeze MCP tools.
Inspect Breeze cache and asset settings through MCP. The purge bridge declares a whole-cache callback, with no URL or post purge candidate.
Driver coverage
Settings and purge support are separate.
These declarations come from the WPPilot Pro driver. A candidate callback must exist on the installed plugin before a purge can run.
- Layer and driver
- page ·
breeze - Declared purge candidates
- all
- Shared settings map
- 12 keys: page_cache.enabled, page_cache.ttl, page_cache.mobile_separate, browser_cache.enabled, css.minify, js.minify, css.combine, js.combine, images.lazyload, images.lazyload_iframes, page_cache.exclusions, preload.links_on_hover
- Native option names or prefixes
- breeze_basic_settings, breeze_advanced_settings, breeze_file_settings, breeze_cdn_integration, breeze_preload_settings
Inspect the returned supported and unsupported settings before selecting a write. Use the plugin interface to review the saved result.
Compare the cache drivers →Operation reference
What WPPilot exposes for Breeze
Use these names to find the exact ability. Read the input and output schema returned by your site before calling it; parameters can change with the installed version.
Cache and page speed · Pro
| Ability | Operation | Source annotation |
|---|---|---|
| wppilot/cache-apply-preset | Apply Cache Preset | Write |
| wppilot/cache-begin-experiment | Begin Cache Experiment | Write |
| wppilot/cache-check-setup | Check Cache Setup | Read |
| wppilot/cache-get-settings | Get Cache Settings | Read |
| wppilot/cache-list-actions | List Cache Actions | Read |
Tasks to try
Start with one change.
- Take a baseline, change one setting, purge, warm, and re-measure
- Read the whole settings row when the canonical keys run out
- Roll a change back to its exact previous values from the change ledger
Before running it
Check the result in Breeze.
Settings that routinely break sites - combining CSS or JavaScript, critical CSS, unused-CSS removal, deferring JavaScript, and caching for logged-in users - are refused without an explicit confirmation, and the refusal names which ones.
Inspect the returned supported and unsupported settings before selecting a write. Use the plugin interface to review the saved result.
These are suggested tasks based on the source. They are not customer case studies or a test of your installation. Keep the target IDs and previous values, then check the saved object and its visible output. Recovery support varies by operation.
Which WPPilot edition includes Breeze?
Breeze support requires WPPilot Free, an active WPPilot Pro licence and the companion plugin or theme where applicable.
What should I check before changing Breeze?
Settings that routinely break sites - combining CSS or JavaScript, critical CSS, unused-CSS removal, deferring JavaScript, and caching for logged-in users - are refused without an explicit confirmation, and the refusal names which ones.
Related modules: LiteSpeed Cache · WP Rocket · WP Fastest Cache
Your site · your policy · your AI client
Connect Breeze to your AI client.
Breeze support requires WPPilot Free, an active WPPilot Pro licence and the companion plugin or theme where applicable.