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.
At a Glance & Executive Verdict
Obsidian Codex MCP
Knowledge & Memory · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
MCP Obsidian
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: API Key required
Verdict Summary: Choose Obsidian Codex MCP if you need specialized Knowledge & Memory tools running via a local process. Choose MCP Obsidian 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: OBSIDIAN_VAULT_PATH, OBSIDIAN_READ_ONLY, OBSIDIAN_BACKUP_ON_WRITE.
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.
MCP server that interacts with Obsidian via the Obsidian rest API community plugin
Category & Scope
Tools & Capabilities Breakdown
Obsidian Codex MCP Tools (17)
configure_vault
set or change the vault path
get_note
read one markdown note by vault-relative path
create_note
create a new markdown note with optional metadata
update_note
update note content and/or frontmatter
delete_note
delete a markdown note
list_notes
list notes in the vault or a folder
search_notes
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, MCP Obsidian belongs to Knowledge & Memory using local stdio subprocess. Select Obsidian Codex MCP when you need capabilities focused on knowledge & memory and MCP Obsidian when you require tools for knowledge & memory.