Obsidian Codex MCP vs Obsidian MCP Server | AllMCPs
Side-by-Side Model Context Protocol Comparison
Obsidian Codex MCP vs Obsidian MCP Server
In-depth architectural comparison of the Obsidian Codex MCP and Obsidian MCP Server 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
Obsidian Codex MCP
Knowledge & Memory · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Obsidian MCP Server
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Verdict Summary: Choose Obsidian Codex MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Obsidian MCP Server 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 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.
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.
SSE-enabled MCP server for remote Obsidian vault management with 29 tools for notes, directories, frontmatter, tags, search, and link operations. Docker-ready with health monitoring.
Category & Scope
Tools & Capabilities Breakdown
Obsidian Codex MCP Tools (6)
Direct filesystem access to markdown notes
Read-only mode to prevent writes
Backup-on-write before updates and deletes
Path traversal protection and vault isolation
Full support for Obsidian Bases (.base) with schema validation
Works with any MCP client via JSON or TOML config
Obsidian MCP Server Tools (31)
read-note
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).
Obsidian Codex MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Obsidian MCP Server belongs to Knowledge & Memory using local stdio subprocess. Select Obsidian Codex MCP when you need capabilities focused on knowledge & memory and Obsidian MCP Server when you require tools for knowledge & memory.