Clear hung custom MCP remotes in Grok Bot

Cursor staff report a catch-22: one hung custom HTTP MCP remote can blank plugin discovery, hide remotes under Plugins → Yours, and make Uninstall time out with DeadlineExceeded. You cannot finish a self-serve delete from that UI while discovery is stuck.

What you can do now

1. Identify the custom remote URL that stopped answering (502/timeouts, hung handshake).
2. Take that endpoint fully offline so every connection refuses (fail closed). A half-dead hang keeps discovery stuck; a hard refuse is the interim staff guidance.
3. Fully quit and relaunch Grok Bot, then reopen Settings → Plugins.
4. If Yours still omits the remote or Uninstall still times out, open a Cursor forum thread (or support) and ask staff to clear the hung remote from the backend. Include Bot name, approximate add time, and the remote URL host.

Staff have cleared hung remotes from the backend when the UI path is blocked. There is no documented user control that bypasses that state.

While you wait

• Prefer official catalog connectors when they cover the job.
• Avoid re-adding the same broken URL until staff confirm the hang is cleared.
• For OAuth redirect failures on a live remote (separate issue), see Fix custom MCP OAuth redirect in Grok Bot.

Pitfalls

• Spamming Uninstall while discovery is blank will not surface a hidden remote.
• Leaving the endpoint soft-hanging (accept then stall) keeps the blank-discovery pattern.
• Do not invent a hidden Settings page for force-delete; staff backend clear is the documented recovery when Yours is empty.