METAGROK
GROK BOT / clear-hung-custom-mcp-remotes-in-grok-bot

Clear hung custom MCP remotes in Grok Bot

clear-hung-custom-mcp-remotes-in-grok-bot

Use this when MCP discovery in Grok Bot hangs for your whole account after you added a custom remote. Cursor staff (mohitjain, Aug 14, Sep 2, Sep 7, and Sep 11, 2026) describe a catch-22: one hung custom HTTP remote can blank MCP discovery for the whole account (DeadlineExceeded on list, search, restart, and uninstall). Those remotes often do not appear in Settings → Plugins → Yours (xAI's docs call this Marketplace → Your plugins; cursor.com/docs/grok-bot/work, checked 2026-09-25; docs.x.ai/grok-bot/settings-and-notifications, checked 2026-09-25) or on the Cursor dashboard Plugins page. As of Sep 2026, staff documented a self-serve Delete user config path on cursor.com/agents that works while discovery is still hung.

Confirm you are in the catch-22

  1. Open Settings → Plugins → Yours (xAI's docs call this Marketplace → Your plugins → Manage plugins and skills) (cursor.com/docs/grok-bot/work, checked 2026-09-25; docs.x.ai/grok-bot/settings-and-notifications, checked 2026-09-25). Search for the custom remote name under Installed. If marketplace connectors still show but the custom URL does not, you may be on a ghost remote.
  2. Ask the Bot to list connectors, restart MCP servers, or uninstall the hung remote. Note Backend MCP tool discovery failed: DeadlineExceeded.
  3. Check cursor.com dashboard Plugins while signed in. Custom Grok Bot remotes added via AddMcpServer are often missing there too.

What you can do now

1. Self-serve: Delete user config (try first). This path does not need the stuck remote to respond, so it works during DeadlineExceeded discovery.

  1. Open cursor.com/agents and start or open an agent so the composer is available.
  2. Click the + menu → MCP Servers.
  3. Open the hung remote (for example user-migadu, user-Crisp) → Delete user config.
  4. Reload. Other connectors should return.

If the remote does not show in that list or Delete user config will not complete, escalate to staff (step 2).

2. Staff clear (fallback). File a Cursor forum bug or support ticket with:

  • Cursor account email and plan
  • Grok Bot agent name and agent id
  • Exact custom remote name, host URL, and likely identifier (for example user-derive)
  • That Uninstall / GetMcpServerStatus / SearchPlugins all return DeadlineExceeded
  • That Delete user config was missing or failed on cursor.com/agents

Staff clear the stuck remotes from the backend and confirm when discovery returns.

3. Interim if you control the endpoint. Take the MCP host fully offline so connections are refused. Staff say a refused connection can unstick discovery while you wait for a backend drop or self-serve delete. A host that hangs open keeps discovery stuck.

Related

Pitfalls

  • Uninstall from the Bot still probes every connector first while discovery is hung, so agent uninstall times out — prefer Delete user config on cursor.com/agents.
  • Marketplace plugins on the same account go dark with the hung remote; clearing the ghost restores them.
  • Canceling the Cursor account is a destructive last resort other users tried; prefer Delete user config, then staff clear.