Kage vs Obsidian Codex Mcp

Side-by-side comparison of two Model Context Protocol servers — install paths, tools, quality signals, and directory engagement so you can pick the right one for Claude, Cursor, and other MCP clients.

Compare
K
Kage
kage-core
🧠 Knowledge & Memory
O
Obsidian Codex Mcp
dot-RealityTest
🧠 Knowledge & Memory
SummaryVerified, git-native memory for coding agents. Memory is plain JSON packets committed in your repo, each checked against the code it cites — hallucinated citations rejected at write, stale or changed memory withheld at recall, plus diff-time stale-catch. Local-only (BM25 + vectors), no account, no API key. npx -y @kage-core/kage-graph-mcp installLocal-first Obsidian vault MCP server for Codex, Claude Desktop, and other MCP clients. Works directly with markdown files, no Obsidian plugin, API key, cloud service, or running Obsidian app required. Includes read-only mode, backup-on-write, path isolation, and setup examples.
Quality signal24/100 (Emerging)25/100 (Emerging)
Install pathnpx · highpip · high
Engagement 0 0 0 0 0 0 9
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView KageView Obsidian Codex Mcp
More alternatives to KageMore alternatives to Obsidian Codex McpKnowledge & Memory categoryCanonical compare URL

Other servers like Kage