MCP Server Connected (Green Dot) and Tools Discovered in Logs, but "0 tools" in UI and Agent

Support Bug Reports
,
8

Hey, thanks for the detailed report with logs, that really helps.

Looks like you hit the same bug as in this thread: [macOS 26] McpProcess IPC crash loop on startup — agent execution fails until legacyMcpMode workaround applied. Your app logs match the exact pattern:

[McpProcess] ipcReady wait failed [...] timed out waiting for ipcReady after 10000ms
[McpProcess] giving up after 6 crashes within 600000ms; falling back to legacy in-window MCP

So the McpProcess utility process crashes 6 times on startup, then Cursor falls back to the legacy in-window MCP path. Your tools get discovered via the legacy fallback, which is why you see the green dot and “discovered 14 tools” in the logs, but they don’t get added to the UI registry correctly. That’s a side effect of the crash.

We’re tracking this issue internally, but there’s no ETA for a fix yet. Stitch MCP isn’t the cause here. You already confirmed stitch-mcp proxy runs fine from Terminal.

A few things that would help with debugging:

  1. Open Console.app, filter for mcpProcess or go to Diagnostics > User Reports, then attach the crash report. It should show the exit code or signal that’s killing the utility process.
  2. When you run Cursor.app/Contents/MacOS/Cursor . from Terminal, do you see trace trap or SIGTRAP in the output? If yes, please share the full stderr.
  3. Confirm your exact macOS 26.x version. Your post says 26.4.1, is that correct? Also confirm your Cursor version. Your logs show 3.4.17, but your post says 3.2.21.

Note: the cursor.agent.legacyMcpMode setting doesn’t exist in Cursor. If you saw it suggested as a workaround, that was a hallucination. There isn’t a manual workaround right now, the fallback happens automatically after about 90 seconds of retrying.