Obsidian Codex MCP vs Deja Vu

In-depth architectural comparison of the Obsidian Codex MCP and Deja Vu 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.

Which MCP Server Should You Choose?

Choose Obsidian Codex MCP when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• You have access to required keys: VAULT_PATH, READ_ONLY, BACKUP_ON_WRITE.
• Primary tools included: Direct filesystem access to markdown notes, Read-only mode to prevent writes, Backup-on-write before updates and deletes.

Explore Obsidian Codex MCP Details

Choose Deja Vu when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: deja.

Feature & Specification Comparison

Specification	Obsidian Codex MCP dot-RealityTest Knowledge & Memory	Deja Vu vshulcz Knowledge & Memory
Summary
Category & Scope	Knowledge & Memory	Knowledge & Memory

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "dot-realitytest-obsidian-codex-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "dot-realitytest-obsidian-codex-mcp"
      ],
      "env": {
        "VAULT_PATH": "YOUR_VAULT_PATH_HERE",
        "READ_ONLY": "YOUR_READ_ONLY_HERE",
        "BACKUP_ON_WRITE": "YOUR_BACKUP_ON_WRITE_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "vshulcz-deja-vu": {
      "command": "npx",
      "args": [
        "-y",
        "@vshulcz/deja-vu"
      ]
    }
  }
}

Related MCP Server Comparisons