Connect Grok to your Locker

Give Grok Build (and other agents) read access to your Locker via MCP. Prefer the native Markdown Locker MCP — search, read, and list notes — over a generic folder mount.

Recommended: native MCP v0

Tools: search_notes, read_note, list_recent. Read-only. Resolves ~/Documents/Markdown Locker, or legacy ~/Markdown Locker, or MARKDOWN_LOCKER_DIR.

From a clone of the repo:

cd /path/to/markdown-locker/mcp
npm install

grok mcp remove markdown-locker 2>/dev/null
grok mcp add markdown-locker -- node "$PWD/src/server.mjs"
grok mcp doctor markdown-locker

Details: github.com/fortblocks/markdown-locker/mcp

Fallback: filesystem MCP

If you only need raw file access (writes possible — be careful):

grok mcp add markdown-locker-fs -- npx -y @modelcontextprotocol/server-filesystem \
  "$HOME/Documents/Markdown Locker"

Legacy installs may use ~/Markdown Locker instead of Documents.

What to try

• “List recent notes in my Markdown Locker.”
• “Search the Locker for and summarise.”
• “Read decisions.md and list open items.”

grok.com Connectors

Grok on the web supports Custom MCP at grok.com/connectors with a public HTTPS URL. Prefer Grok Build + local MCP for private notes. Do not tunnel your Locker to the public internet. See also Connect grok.com.

Safety

• Native MCP is read-only and scoped to the Locker root.
• Filesystem MCP may allow writes — review tool prompts.
• Never point MCP at $HOME as a whole.

Positioning: Notes for AI agents · Local-first · Discovery map: /llms.txt