Controlling Super Speedy Chat with MCP
Connect Super Speedy Chat to Codex or Claude Code and you can ask it to check chat health, waiting visitors, availability and relay configuration, then make controlled operational changes without exposing stored API tokens.
Requires Super Speedy Chat 1.13.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 Chat.
- 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 or reuses a dedicated Super Speedy Agent user, grants the selected plugin capabilities, and generates a revocable WordPress Application Password plus a version-pinned command for the shared Node.js 18+ bridge. Execute and plugin-install capabilities are separate opt-ins. One connection exposes the permitted abilities from every active Super Speedy plugin.
Ask for chat health first. A waiting visitor, unavailable schedule, relay failure and missing database table are different problems and should not be fixed with the same setting change.
Useful requests
- “Check whether chat is available now and explain why.”
- “Are any visitors waiting for a reply?”
- “Diagnose the last WhatsApp relay failure.”
- “Show me the proposed opening-hours or relay change before applying it.”
What the assistant should do
The assistant should read status and configuration first. It can report database readiness, current availability and its reason, waiting-conversation count, enabled relays and the last WhatsApp send error. For a configuration change it should preserve masked secrets, explain visitor-facing consequences, request confirmation where required, then verify the stored settings and health.
API tokens can be rotated, but they cannot be read back through MCP.
MCP abilities
| Ability | Purpose |
|---|---|
get-status | Read table health, availability, waiting count, relay switches and the last WhatsApp error. |
get-config | Read supported operational settings; secrets are reported only as set or not set. |
update-config | Update recognised settings and rotate write-only credentials. |
These abilities use the super-speedy-chat namespace and are discovered through the shared connection.
Safety
The abilities require ssc_manage, granted to administrators automatically. Discord, WhatsApp and LLM tokens are write-only and masked on reads; writing the mask back preserves the stored value. Disabling chat, requiring login, changing opening hours and changing relay switches require explicit confirmation. Appearance and Ajax transport settings are intentionally outside this MCP surface because they require visual work or have installation side effects.
When MCP does not cover the task
Use browser control to test the visitor and operator interfaces, visual styling, responsive layout or the real login flow. Restricted SSH can inspect server logs and relay callbacks. Keep normal health checks and operational settings within MCP.
Troubleshooting the connection
- If the abilities are missing, activate or update Super Speedy Chat and restart the AI assistant.
- If connection generation is unavailable, check HTTPS and WordPress Application Password support.
- If a relay appears enabled but fails, inspect the status error before rotating credentials; the fault may be transport or provider-side.
Comments