Controlling Scalability Pro with MCP
Connect Scalability Pro to Codex or Claude Code and you can ask it to measure the site, explain the available optimisations, apply safe changes, and verify the result instead of switching options blindly.
Requires Scalability Pro 6.27.1 or newer and WordPress 6.9 or newer.
Connect once for all Super Speedy plugins
MCP setup is shared across the Super Speedy range. You do not need a separate bridge for Scalability Pro.
- Install any Super Speedy plugin, open Super Speedy, and enter your licence.
- Open Super Speedy > MCP setup.
- Generate the connection commands and copy the command for Codex or Claude Code.
- Paste it into your terminal, then restart the AI assistant.
The setup page creates a revocable WordPress Application Password. One connection exposes every documented ability registered by the active Super Speedy plugins.
Ask the assistant to record a baseline, state the change it proposes, and repeat the same measurements afterwards. A faster result is more useful than a longer list of enabled settings.
Useful requests
- "Measure the important pages and recommend the safest Scalability Pro improvements."
- "Show me which recommended database indexes are missing."
- "Apply the safe settings, then repeat the same measurements."
- "Explain the risk and expected benefit of this experimental setting before changing it."
What the assistant should do
A good optimisation pass starts with settings descriptions, current settings, index status and representative measurements. The assistant should separate safe changes from confirmation-gated changes, apply only the agreed scope, then repeat the same probes and report the before-and-after result. It should not claim a general speed improvement from a single unrelated page.
MCP abilities
| Ability | Purpose |
|---|---|
get-settings | Read the stored settings with documented defaults filled in. |
describe-settings | Explain the type, default, accepted values, risk and meaning of each supported setting. |
measure | Time up to ten same-site URLs and selected safe database probes. |
get-index-status | Report which managed database indexes are installed. |
set-settings | Update one or more settings classified as safe. |
apply-setting | Apply one confirmation-gated setting or index operation. |
describe-recommended | Show the good-settings plan, including what it applies and deliberately leaves alone. |
apply-recommended | Apply the confirmed good-settings plan, with staged before-and-after measurement when Performance Analysis is active. |
scan-options | Load selected key pages through signed loopback requests and record the options they actually use. |
get-options-plan | Propose autoload changes from the latest scan without changing anything. |
apply-options-plan | Apply a confirmed autoload plan and record every change for reversal. |
revert-options-plan | Restore the exact previous autoload values from the change log. |
The assistant should still discover the live surface rather than rely on a hard-coded client list, because new guided optimisation abilities can appear without changing the connection.
Safety
Reading and safe writes require spro_manage; risky changes require spro_apply. Administrators receive both automatically. Risky settings cannot be hidden inside a batch: each must be sent through the confirmation-gated path. Index work uses an operation lock so two workers cannot change the same structure concurrently. The abilities affect plugin settings and managed indexes, not posts, customers or orders.
When MCP does not cover the task
Use browser control to reproduce a front-end symptom, inspect waterfalls or confirm visual correctness. Restricted SSH is suitable for database process inspection, PHP logs and WP-CLI work. Give an AI assistant the narrowest SSH account and permissions that still cover the diagnosis.
Troubleshooting the connection
- If abilities are missing, activate or update Scalability Pro and restart the AI assistant.
- If connection generation is unavailable, check HTTPS and WordPress Application Password support.
- If a risky setting is refused, use the dedicated confirmed action rather than trying to include it in a safe batch.
Comments