Obsidian MCP Server vs Obsidian Codex MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Obsidian MCP Server vs Obsidian Codex MCP
In-depth architectural comparison of the Obsidian MCP Server 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
Obsidian MCP Server
Knowledge & Memory · Local stdio
Quality: 61/100 (Good) | Auth: No auth required
Obsidian Codex MCP
Knowledge & Memory · Local stdio
Quality: 44/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Obsidian MCP Server 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 Obsidian MCP Server 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).
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.
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.
Category & Scope
Tools & Capabilities Breakdown
Obsidian MCP Server Tools (31)
read-note
Read note contents (supports `frontmatterOnly` for efficiency)
read-multiple-notes
Batch read multiple notes
create-note
Create a new note
edit-note
Replace note contents
write-note
Write with modes: overwrite, append, or prepend
delete-note
Delete a note (requires confirmation)
move-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 MCP Server 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 Obsidian MCP Server when you need capabilities focused on knowledge & memory and Obsidian Codex MCP when you require tools for knowledge & memory.