Perfmatters MCP tools.
Read Perfmatters option rows and edit existing native keys. Shared setting meanings are unverified, and there is no cache to purge.
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
- asset ·
perfmatters - Declared purge candidates
- None. Use the plugin or hosting controls where a purge is needed.
- Shared settings map
- No canonical map. Native option keys do not carry verified cross-plugin meanings.
- Native option names or prefixes
- perfmatters_options, perfmatters_tools, perfmatters_script_manager
Native option reads and edits are implemented, but key meanings have not been verified against a licensed installation. There is no canonical settings map. Re-read each value and check the browser after a change.
Compare the cache drivers →Operation reference
What WPPilot exposes for Perfmatters
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.
- Quote the live configuration while diagnosing a slow page
- Purge it together with every other layer after an edit
- Compare its settings against a second optimiser stacked on the same site
Before running it
Check the result in Perfmatters.
Writes are refused rather than guessed. The option keys are unconfirmed without a licensed install, and a wrong guess here lands on script-disabling and JavaScript-delay settings.
Native option reads and edits are implemented, but key meanings have not been verified against a licensed installation. There is no canonical settings map. Re-read each value and check the browser after a change.
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 Perfmatters?
Perfmatters support requires WPPilot Free, an active WPPilot Pro licence and the companion plugin or theme where applicable.
What should I check before changing Perfmatters?
Writes are refused rather than guessed. The option keys are unconfirmed without a licensed install, and a wrong guess here lands on script-disabling and JavaScript-delay settings.
Related modules: LiteSpeed Cache · WP Rocket · WP Fastest Cache
Your site · your policy · your AI client
Connect Perfmatters to your AI client.
Perfmatters support requires WPPilot Free, an active WPPilot Pro licence and the companion plugin or theme where applicable.