Obsidian Codex MCP vs Cortex Plugin

In-depth architectural comparison of the Obsidian Codex MCP and Cortex Plugin 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 Cortex Plugin 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: .

Feature & Specification Comparison

Specification	Obsidian Codex MCP dot-RealityTest Knowledge & Memory	Cortex Plugin TT-Wang Knowledge & Memory
Summary	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.	Persistent, self-evolving memory plugin for Claude Code. Background miner extracts durable lessons (decisions, conventions, bug fixes) from completed sessions via Claude Haiku, stores them as human-readable markdown in an Obsidian vault, and assembles query-tailored context briefings at session start. Local-first, no cloud, no API keys. Self-healing install via uv bootstrap shim, /cortex-doctor preflight, graceful FTS-only degraded mode when claude CLI missing. MIT.

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": {
    "tt-wang-cortex-plugin": {
      "command": "pipx",
      "args": [
        "install",
        "memem"
      ],
      "env": {
        "MEMEM_TELEMETRY_SOURCE": "YOUR_MEMEM_TELEMETRY_SOURCE_HERE"
      }
    }
  }
}

Related MCP Server Comparisons