Connect grok.com to your Locker
Grok on the web supports Custom MCP connectors. That is different from Grok Build on your Mac. Choose the path that matches how private your notes are.
Recommended default
For a private Locker on your machine, use Grok Build + local MCP (stdio — no public URL). That keeps notes on disk and agents attached locally. See Connect Grok Build.
What grok.com needs
At grok.com/connectors
→ New Connector → Custom, Grok asks for an MCP server URL.
xAI’s servers must reach that URL on the public internet.
localhost and private LAN addresses are rejected.
So web Grok cannot talk to a pure local stdio process the way Grok Build can. You either expose an HTTP MCP endpoint (tunnel or host), or stay on Grok Build.
Optional: tunnel (power users)
A tunnel (e.g. ngrok) can forward a local HTTP MCP port to a temporary HTTPS URL. xAI documents this under Custom MCP tunneling. Only do this if you understand the risk: anything that can hit that URL can attempt your MCP tools while the tunnel is up.
- Run an HTTP/SSE MCP server scoped to the Locker (not your whole home directory).
- Prefer read-only tools.
- Use a short-lived tunnel; turn it off when you are done.
- Do not treat tunneling as the product default for private notes.
Markdown Locker’s shipping MCP v0 is stdio for Grok Build. An HTTP transport for web connectors is a separate path — not required for local agents.
Skills (no tunnel)
Grok Skills can teach agents how the Locker works (paths, frontmatter, Versioned Save, when to use MCP)
without exposing files. A skill pack lives in the repo under
skills/markdown-locker/. Skills are instructions; they do not replace MCP for reading your notes.
Our stance
Local notes agents can trust. We optimise for attach-on-your-machine first. Web connectors are possible via public MCP URLs; we will not pretend localhost is enough for grok.com, and we will not recommend opening your vault widely.