GoodMemory 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
G
🧠 Knowledge & Memory
O
Obsidian Codex Mcp
dot-RealityTest
🧠 Knowledge & Memory
SummaryLocal-first, auditable memory layer for Codex, Claude Code, and MCP clients. Stores scoped user/project memory in SQLite or Postgres, exposes read-only recall, trace, stats, and artifact tools by default, and supports opt-in governed writeback with review, forget, and audit controls. Published as io.github.hjqcan/goodmemory in the official MCP Registry.Local-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 · lowpip · high
Engagement 0 0 0 0 0 0 9
ToolsNot listed yetNot listed yet
Verified / officialNoNo
Open listingView GoodMemoryView Obsidian Codex Mcp
More alternatives to GoodMemoryMore alternatives to Obsidian Codex McpKnowledge & Memory categoryCanonical compare URL

Other servers like GoodMemory