Obsidian Codex Mcp vs Kage

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
O
Obsidian Codex Mcp
dot-RealityTest
🧠 Knowledge & Memory
K
Kage
kage-core
🧠 Knowledge & Memory
SummaryLocal-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.Verified, 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 install
Quality signal25/100 (Emerging)24/100 (Emerging)
Install pathpip · highnpx · high
Engagement 0 0 0 9 0 0 0
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView Obsidian Codex McpView Kage
More alternatives to Obsidian Codex McpMore alternatives to KageKnowledge & Memory category

Other servers like Obsidian Codex Mcp