How to use Super Speedy MCP
Super Speedy MCP gives Codex, Claude and other compatible AI assistants a managed set of tools for inspecting and configuring your Super Speedy plugins. Instead of clicking through settings screens or learning command names, you connect the site once and describe the result you want.
MCP is usually the best route for repeated plugin work because each action has defined inputs and results, access can be restricted, and sensitive changes can require confirmation. It is not the only route. Chrome is simpler for occasional dashboard work and covers anything visible in WordPress, while SSH is more powerful when a developer needs WP-CLI or server access. See Setting up a store with an AI assistant for the full comparison.
Use MCP for repeatable Super Speedy plugin work. Add Chrome when a task has no MCP tool, or use restricted SSH when it genuinely needs WP-CLI, files or other server tools.
What MCP means on your WordPress site
MCP stands for Model Context Protocol. It is a standard way for a plugin to give an AI assistant a documented set of tools. Super Speedy plugins register their tools through the WordPress Abilities API, then the MCP connection makes those tools available to the assistant.
This is different from browser control. With Chrome, the assistant finds fields and clicks buttons on the current screen. With MCP, it calls a specific action such as reading a plugin configuration, planning filters or checking an import. The result comes back as structured data, so the assistant can verify what happened without guessing from the page layout.
The quickest way to connect
- Install any Super Speedy plugin on the site.
- Enter your licence on the Super Speedy Plugins settings page.
- Open the MCP setup page and copy the command shown there.
- Paste the command into your terminal.
- Open Codex or Claude Code and ask it to list the Super Speedy tools available on the site.
Starting with one Super Speedy plugin is enough. The shared tools can see the rest of the range and install another Super Speedy plugin through your licence when it is needed. Installation requires confirmation and is recorded in the install log.
Copy the command generated by the MCP setup page. It already contains the connection details, so you do not need to build an MCP configuration or copy individual endpoint addresses by hand.
Ask for the result, not the tool
You do not need to know the internal MCP or ability names. Ask for the outcome in ordinary language, for example:
Show me which Super Speedy plugins are installed and whether my licence is working.Configure infinite scroll on my blog and verify that it loads the next page correctly.Plan sensible filters for my WooCommerce catalogue, but do not create them yet.Migrate my imports from WP All Import to Super Speedy Imports.Speed up my website and show me the plan before changing anything.
The assistant discovers the available tools, inspects the current site, explains its plan, asks for confirmation where required, makes the change and verifies the result.
What Super Speedy MCP can do
Every current Super Speedy plugin carries the shared tools needed to:
- list which Super Speedy plugins are installed and active;
- check whether the site has a licence;
- install and activate another Super Speedy plugin from the licensed update server;
- show the plugin-install audit log.
The install tool accepts a Super Speedy plugin slug, not an arbitrary download URL. The licensed update server resolves the package, the download host is restricted, and installation needs an explicit confirmation step.
Tools belonging to each plugin
Each plugin exposes the actions that make sense for it. Many provide structured configuration reading and writing. Others add purpose-built tools, such as planning filters, inspecting an archive for the CSS selectors Auto Infinite Scroll needs, measuring performance, previewing an email audience or checking a sitemap cache.
The assistant only gets the actions a plugin deliberately exposes. MCP does not silently grant general access to every WordPress screen, post, file or database table.
When MCP does not cover the job
Use another connection alongside it rather than trying to force the task through the wrong tool.
| Route | Best for | Main trade-off |
|---|---|---|
| Super Speedy MCP | Repeatable plugin configuration, migrations and checks | Limited to the actions plugins expose |
| Chrome control | Occasional dashboard work and screens with no MCP tool | Depends on the current layout and works through forms one click at a time |
| General WordPress MCP | Articles, media and wider WordPress maintenance | Needs a suitable general WordPress MCP plugin |
| Restricted SSH with WP-CLI | Plugin installation, code, logs, bulk work and debugging | Much broader server access, so it needs more care |
Chrome is the quickest fallback because it can use the same signed-in dashboard you use. SSH can install other WordPress plugins and server tools, but should normally use a dedicated non-root account, key authentication, staging and a current backup.
Security and staying in control
MCP is site administration over an API, so use the narrowest access that can complete the task:
- Use a dedicated WordPress user. Grant only the capabilities needed for the plugins the assistant will manage instead of defaulting to a full administrator account.
- Use revocable credentials. Application passwords and MCP tokens can be revoked without changing your normal WordPress password.
- Inspect first. Ask the assistant to report the current state and show its plan before it writes anything.
- Confirm sensitive operations. Plugin installation and explicitly sensitive settings require a deliberate confirmation step.
- Review the result. Settings remain visible in the normal WordPress interface and plugin installations are recorded in an audit log.
- Use staging for risky work. Imports, code changes, database work and bulk updates should be tested away from the live site wherever possible.
Super Speedy configuration tools do not automatically gain access to posts, customers or orders. If you want general content maintenance, add a suitably restricted WordPress MCP plugin or use Chrome. Do not widen the connection just because one task falls outside the Super Speedy tools.
Advanced connection routes
The generated setup command is the normal route. Technical users can also expose the same underlying WordPress abilities in two ways:
- AI Engine MCP: If the site runs AI Engine with its MCP module enabled, Super Speedy abilities appear alongside its other WordPress tools on the same MCP connection.
- WordPress REST directly: Abilities can be called through the WordPress REST API using a dedicated user’s Application Password. Read-only abilities use GET and writing abilities use POST. This is useful for custom scripts and integrations rather than an ordinary first setup.
Both routes use the same registered abilities and permission checks. They are alternatives to handing an assistant unrestricted server access.
Worked example: infinite scroll on a blog
Auto Infinite Scroll works on the standard shop and product archives out of the box. If a blog or custom listing needs different selectors, you can ask:
Make infinite scroll work on my blog at /blog/ and verify it.
The assistant then:
- reads the current Auto Infinite Scroll configuration;
- inspects
/blog/and counts what the current selectors match; - identifies candidate container, pagination and next-page selectors;
- adds the new selectors alongside the defaults;
- inspects the page again and confirms the selectors now match.
The worked example requires Auto Infinite Scroll 1.72 or newer. The archive inspector is limited to the same site, and replacing the built-in CSS selectors is treated as a sensitive change.
Controlling each plugin from an assistant
Each guide explains what the plugin can read, what it can change and which operations have extra safety checks.
- Scalability Pro – tune settings by risk level and measure pages before and after
- Super Speedy Search – run real searches, explain rankings and adjust search tuning
- External Images – audit catalogue images and verify supplier URLs
- Delayed Image Import – monitor the hydration backlog and adjust download behaviour
- Super Speedy Sitemaps – manage sitemap settings and flush the cache
- Super Speedy Ajax Prices – configure live prices and check transport health
- Super Speedy Emails – draft, preview and rehearse email work safely
- Super Speedy Chat – manage availability, relays and chat health
- Super Speedy Coming Soon – inspect product gates and waitlists
- Auto Infinite Scroll – configure new archive types without writing selectors by hand
- Fullscreen Typeform – manage defaults and inspect page overrides
Troubleshooting the connection
If the tools do not appear:
- Confirm the site runs WordPress 6.9 or newer.
- Update the Super Speedy plugin.
- Confirm the licence is entered on the site.
- Check that the connected WordPress user has the required plugin capability.
- Copy the current command from the MCP setup page again, reconnect and restart the assistant.
- Ask the assistant to list the available tools before asking it to change anything.
If the connection works but one operation is missing, that plugin may not expose the action. Use Chrome for the WordPress screen or restricted SSH for a genuine server task. If you are still stuck, contact Super Speedy support.
Comments