Troubleshoot MCP connections
Updated October 8, 2026 · 2 min read
On this page
Start by asking your coding agent to call get_context. A successful response confirms the workspace and granted permissions.
Connection problems
Problem | What to check |
Supahelp tools do not appear | Save the supplied configuration in the chosen agent's file and restart the agent |
Agent cannot authenticate | Check the token, expiry, and revocation status; browser sign-in is separate |
Wrong workspace | Create the connection in the intended workspace and replace that agent's Supahelp configuration |
Token was lost | Create a replacement and revoke the old connection; tokens cannot be recovered |
Copy failed | Select and copy the visible value manually |
Connection creation failed | Check your role and the limit of ten active connections per person per workspace |
MCP_DISABLED | MCP or the requested operation is not enabled for this workspace; contact Supahelp support |
Read works, editing or publishing does not | Check the connection permissions and your current workspace role |
The current setup page supplies a configuration containing the token. If you previously configured Codex to use an environment variable, follow the page's instruction to remove bearer_token_env_var when switching to the supplied configuration. Keep only one Supahelp configuration block.
Draft and publication problems
Problem | What to do |
Pagination cursor is stale | Restart listing from the first page; the draft or publication changed |
Draft version changed | Reread the current draft, then reapply the intended edits |
Preview expired or changed | Review a fresh preview before publishing |
Validation failed | Preserve Supahelp's rich content format and valid image or asset references |
Rate limited | Wait before retrying |
Agent refuses publication | Use a session that allows review and approval, or publish yourself in the editor |
If a publication response reports cacheRefresh: retry_needed, publication has committed but refreshing the public cache needs a retry. Ask the agent to retry the same request with the same idempotency key and preview token. Do not assume that no response means nothing was published.
If a save or publish response is lost, the agent should retry with the same key and exact arguments. A new edit or a newly reviewed publication needs a new key.
Revoke or replace a connection
Open Settings → AI Configuration → Coding agent connections and select Revoke beside the connection.
Owners and admins can revoke workspace connections. Editors can manage their own connections. To rotate a token, create a replacement, verify that it works, then revoke the old one.
Revoking prevents further access. It does not undo saved drafts or published changes.