Obsidian Codex MCP vs MCP Obsidian

In-depth architectural comparison of the Obsidian Codex MCP and MCP Obsidian 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 MCP Obsidian 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: Local stdio MCP access to an Obsidian vault, Note reading, writing, patching, moving, and deletion, Multi-word search with BM25 reranking.

Feature & Specification Comparison

Specification	Obsidian Codex MCP dot-RealityTest Knowledge & Memory	MCP Obsidian bitbonsai 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.	Universal AI bridge for Obsidian vaults using MCP. Provides safe read/write access to notes with 11 comprehensive methods for vault operations including search, batch operations, tag management, and frontmatter handling. Works with Claude, ChatGPT, and any MCP-compatible AI assistant.
Category & Scope

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": {
    "bitbonsai-mcp-obsidian": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/inspector"
      ]
    }
  }
}

Related MCP Server Comparisons