Controlling Super Speedy Sitemaps with MCP
Connect Super Speedy Sitemaps to Codex or Claude Code and you can ask it to review what the sitemap index contains, adjust the main generator settings, and flush cached files so an agreed change takes effect immediately.
Requires Super Speedy Sitemaps 1.10.6 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 connection for Super Speedy Sitemaps.
- 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 generated command uses a revocable WordPress Application Password. One connection exposes the documented abilities from every active Super Speedy plugin.
Ask the assistant to read the configuration, show the proposed change, flush the cache after applying it, then fetch the sitemap index in a browser to verify the visible result.
Useful requests
- "Review my sitemap configuration and flag anything risky for a large catalogue."
- "Why are taxonomy URLs missing from the sitemap index?"
- "Change the URL limit to this value, flush the cache and verify the index."
- "Explain which settings MCP can change and which remain on the advanced screens."
What the assistant should do
The assistant should read the configuration first and distinguish a disabled sitemap type from a stale cached file. It should explain the effect of a URL-limit or taxonomy change, request confirmation where required, update only the agreed settings, flush the sitemap cache, then verify the index URL.
Flushing is safe and repeatable. It clears generated sitemap files; the next request rebuilds them.
MCP abilities
| Ability | Purpose |
|---|---|
get-config | Read main generator settings, current values, defaults and accepted values. |
update-config | Update recognised settings using the plugin’s validation rules. |
flush-cache | Clear generated sitemap files and return the sitemap index URL. |
These abilities use the super-speedy-sitemaps namespace and are discovered through the shared connection.
Safety
The abilities require sssm_manage, granted to administrators automatically. The per-sitemap URL limit requires explicit confirmation because an excessive value can cause timeouts or memory failures on a large site. Disabling taxonomy sitemaps also requires confirmation because it removes all term URLs from the sitemap index. Google News and image extensions, cache-directory controls and other server-level advanced options remain outside this MCP surface.
When MCP does not cover the task
Use browser control to fetch the sitemap index and inspect generated XML. Restricted SSH is appropriate for permissions, cache-directory issues, web-server errors or very large generated files. Normal generator settings and cache flushing should stay within MCP.
Troubleshooting the connection
- If the abilities are missing, activate or update Super Speedy Sitemaps and restart the AI assistant.
- If connection generation is unavailable, check HTTPS and WordPress Application Password support.
- If a configuration change is stored but not visible, flush the sitemap cache before looking for a deeper fault.
Comments