MCPs/Plugins not working

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

ince ~8:29 AM America/Boise on Wed Aug 12, 2026, every MCP lifecycle/discovery call from this Grok Bot agent fails with Backend MCP tool discovery failed: DeadlineExceeded (or tool call timeout ~840s). Calls never reach auth or tool execution. status.cursor.com showed All Systems Operational during the outage; no matching open incident.

Symptoms

GetMcpServerStatus → DeadlineExceeded
GetMcpTools → timeout / DeadlineExceeded
SearchPlugins → DeadlineExceeded / timeout
RestartMcpServers → DeadlineExceeded (restart never starts)
Affects all plugins/connectors, not a single server (ClickUp, Gmail, Calendar, etc.)
ClickUp plugin package is present in local plugin cache on the agent machine, but MCP discovery never lists/connects it
No ClickUp (or Gmail) credential file appears under this agent’s connector-secrets (only telegram, n8n, elevenlabs, tldv observed)
What still works

Direct REST / API outside MCP (e.g. Telegram Bot API via stored token, n8n REST via API key)
Normal chat / routines that don’t need MCP
Shell / local filesystem on the agent computer
Timeline (America/Boise)

~8:29 AM — Weekday Gmail digest routine failed: MCP discovery DeadlineExceeded (first clear hit today)
Morning–afternoon — repeated quiet failures on any MCP attempt; ClickUp workflows previously put on hold for the same class of timeout
~12:54–1:00 PM — User asked to retest after an update; still DeadlineExceeded
~1:00 PM — User approved RestartMcpServers; restart itself failed with the same discovery DeadlineExceeded
Ongoing through at least ~1:04 PM
Repro

Open Grok Bot agent chat (NovaBOT).
Ask agent to list connector status / use ClickUp or Gmail MCP.
Observe GetMcpServerStatus / SearchPlugins / GetMcpTools fail with DeadlineExceeded before any tool schema or auth card.
Expected
MCP discovery returns installed servers/tools (or needsAuth) within normal latency; RestartMcpServers reconnects servers.

Actual
Discovery layer times out; no server list, no auth cards, no tool calls. Restart cannot run.

Workarounds tried

Retries across several hours
Retest after user-reported update
RestartMcpServers (failed at discovery)
Confirmed status.cursor.com green (no active MCP incident matching this)
Ask
Please investigate Grok Bot MCP discovery backend timeouts for this account/agent, and whether a server-side restart or rollback is needed. Happy to provide agent id / run ids if useful.

Agent context

Agent name: NovaBOT
User timezone: America/Boise
Date of issue: 2026-08-12

Steps to Reproduce

Open Grok Bot agent chat (NovaBOT).
Ask agent to list connector status / use ClickUp or Gmail MCP.
Observe GetMcpServerStatus / SearchPlugins / GetMcpTools fail with DeadlineExceeded before any tool schema or auth card.

Expected Behavior

Should connect to plugins

Screenshots / Screen Recordings

Image 8-12-26 at 1.06 PM.png
Image 8-12-26 at 1.06 PM.png1632×1602 270 KB

Operating System

MacOS

Version Information

Grok Bot 0.16.0

Does this stop you from using Cursor

Yes - Cursor is unusable

7

Hi @Wyatt_Baguley Thank you for the post and thanks for being a beta user of Grok Bot!

One of your connectors, the one pointing at gtmplanetary.ngrok.app, is accepting connections but never responding. Discovery runs all of your connectors under a single shared time budget, so when one stops answering, the whole call times out, and every connector comes back empty. RestartMcpServers goes through that same path, which is why it cannot get through either, and why recreating the box changed nothing.

To unblock yourself, remove or disable that connector and ask the agent to list your connectors again. The rest should come back. If you want to keep it, check that its MCP endpoint replies to an initialize request. REST calls to that host succeeding does not mean the MCP route does.

Your Slack connector is also failing, but it fails instantly rather than hanging, so it is not the cause here. On our side, one unresponsive connector should ideally not blank out the rest. That is an issue we are tracking, and I will post here when I have an update.

8

Is that in cursor or Grok bot? Because I don’t have n8n on that one.

9

Nevermind, just took a minute for it to upload. I removed it and everything is working.

Now to test the heck out of this thing. SO FAR IT"S AMAZING. Cancelled my claude and moved to Cursor Ultra, hoping grok bot stays with that subscription.

11

And thank you

12

Hi @Wyatt_Baguley Thanks for the kind words! We’re excited to see what you use Grok Bot for, come back and let us know here!