Hi.
It looks like Grok Bot only supports remote MCP connectors, not local ones that run on my machine (localhost / stdio) — like Workflowy Local MCP. Claude Cowork / Cursor IDE can use those local servers; Grok Bot apparently can’t, since the Bot doesn’t run on my computer.
Is that right? Is local MCP planned, or is remote + the Bot’s cloud browser the intended path?
Would love any feedback.
Steven
Hi @Steven_Hertz Welcome to Grok Bot!
You’re reading this correctly. Grok Bot does not attach MCP servers that run on your own machine, whether that’s stdio or something listening on localhost. The Bot works from a persistent cloud computer, so those local processes aren’t reachable from it.
That’s the intended path today: remote HTTP/SSE MCP and catalog connectors where they exist, and the Bot’s cloud browser everywhere else. Cursor IDE can still use local MCP servers, such as Workflowy Local MCP.
For Workflowy in Grok Bot, the practical option is to have the Bot work in workflowy.com through the Agent Computer browser. Sign in there if it asks you to take over. If a remote Workflowy MCP endpoint shows up later, you can add that as a custom connector.