In-depth architectural comparison of the Basic Memory and Obsidian Codex MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Basic Memory
Knowledge & Memory · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
Obsidian Codex MCP
Knowledge & Memory · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Basic Memory if you need specialized Knowledge & Memory tools running via a local process. Choose Obsidian Codex MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Basic Memory when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Freemium).
Basic Memory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Obsidian Codex MCP belongs to Knowledge & Memory using local stdio subprocess. Select Basic Memory when you need capabilities focused on knowledge & memory and Obsidian Codex MCP when you require tools for knowledge & memory.
Persistent, local-first AI memory: a semantic knowledge graph of plain Markdown files that humans and LLMs both read and write. Works with any MCP client, with optional cloud sync and team workspaces.
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.