mirror of
https://github.com/DeusData/codebase-memory-mcp.git
synced 2026-11-05 08:23:53 +08:00
Martin Vogel
72ee88054f
Grok Build (xAI's grok CLI/TUI) already reached codebase-memory-mcp through its Claude/Cursor compat layer, but a Grok-only user got nothing. Detect $GROK_HOME (default ~/.grok) or a grok CLI and install: - an owned [mcp_servers.codebase-memory-mcp] managed block in config.toml; a same-name foreign table is left byte-identical because a second header would make Grok reject the whole file, while the known owned shape written by `grok mcp add` is adopted. No env forwarding: grok 1.0.5 passes the full parent environment to stdio servers (verified), unlike Codex (#1562). - an owned rules file under $GROK_HOME/rules/ (always scanned, all projects) - the shared skill under $GROK_HOME/skills/ - Scout/Verify/Auditor agents with named-server mcpInheritance and the tier allowlist spelled out as the server__tool ids Grok's search_tool/use_tool dispatcher accepts (inheritance filters per server, never per tool) - hooks withheld: Grok's passive events discard stdout and PreToolUse honors only deny/rewrite decisions, so there is no context-output contract. Verified against grok 1.0.5: inspect discovers the server, agents, skill and rules; mcp doctor handshakes and discovers 15 tools. --clients=grok token, README/npm/llms/landing-page matrices (43 -> 44 surfaces), and smoke coverage. Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>