Why Grok Bot does not attach local MCP
Grok Bot will not attach MCP servers that run on your own machine — stdio packages, localhost listeners, or tools such as Workflowy Local MCP. Staff (kevinn, Aug 13, 2026) stated the intended path on forum 168182: the Bot works from a persistent cloud computer, so processes on your laptop are unreachable from it.
What works today
| Path | Use when |
|---|---|
| Remote HTTP/SSE MCP or catalog connectors | The server has a public URL Grok Bot can reach |
| Agent Computer browser | The product only exists as a website (for example workflowy.com) and you sign in when the Bot asks you to take over |
| Cursor IDE local MCP | You need stdio / localhost servers on the machine where Cursor runs |
Add a public custom connector with Add a custom MCP connector on grok.com when you have a hosted endpoint. Site-only products without MCP follow Use Grok Bot on a website that has no connector.
Stdio paths on the Agent Computer
A stdio MCP installed inside the Agent Computer is a different failure mode from laptop-local MCP. Spawns that still point at a deleted per-bot secrets folder are covered in When stdio MCP points at deleted agent secrets.
Pitfalls
- Installing an npm stdio MCP on your Mac and expecting Grok Bot Plugins to list it.
- Treating Cursor IDE Connected status for a local server as proof Grok Bot can use the same config.