Swift Performance MCP tools.
Inspect Swift Performance option rows and its whole-cache purge callback. Check native keys against the installed edition.
Swift Performance and Swift Performance Lite
WPPilot detects the two editions separately as swift_performance and swift_performance_lite. Both use the swift_performance option prefix and declare a whole-cache purge through Swift_Performance_Cache::clear_all_cache(). Neither has a canonical settings map.
Use the detected edition and native keys reported by your installation. Shared storage and a shared purge method do not establish that Lite includes the paid edition's features. This page covers both drivers so their common behavior has one reference.
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 ·
swift_performance - Declared purge candidates
- all
- Shared settings map
- No canonical map. Native option keys do not carry verified cross-plugin meanings.
- Native option names or prefixes
- swift_performance
No stable option contract across its editions, so nothing is mapped. Its option rows are readable and writable by name.
Compare the cache drivers →Operation reference
What WPPilot exposes for Swift Performance
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.
- Find every caching layer stacked on the site before changing one
- Read its stored configuration by name while diagnosing stale content
- Purge it together with the page cache so the site stops serving a mix of old and new
Before running it
Check the result in Swift Performance.
Its settings are reachable by their own key names and nothing more: no cross-plugin meaning, no risk tier, so verify every change in a browser.
No stable option contract across its editions, so nothing is mapped. Its option rows are readable and writable by name.
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 Swift Performance?
Swift Performance support requires WPPilot Free, an active WPPilot Pro licence and the companion plugin or theme where applicable.
What should I check before changing Swift Performance?
Its settings are reachable by their own key names and nothing more: no cross-plugin meaning, no risk tier, so verify every change in a browser.
Related modules: LiteSpeed Cache · WP Rocket · WP Fastest Cache
Your site · your policy · your AI client
Connect Swift Performance to your AI client.
Swift Performance support requires WPPilot Free, an active WPPilot Pro licence and the companion plugin or theme where applicable.