In-depth architectural comparison of the MCP Obsidian 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
MCP Obsidian
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: API Key required
Obsidian MCP Server
Knowledge & Memory · Local stdio
Quality: 60/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Obsidian 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 MCP Obsidian when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: OBSIDIAN_API_KEY.
Primary tools included: List vault files and directories, Read individual note contents, Search text across vault files.
MCP server that interacts with Obsidian via the Obsidian rest API community plugin
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
MCP Obsidian Tools (6)
List vault files and directories
Read individual note contents
Search text across vault files
Insert or append note content
Delete vault files or directories
Target headings, block references, and frontmatter fields
Obsidian MCP Server Tools (31)
read-note
Read note contents (supports `frontmatterOnly` for efficiency)
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).
MCP Obsidian 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 MCP Obsidian when you need capabilities focused on knowledge & memory and Obsidian MCP Server when you require tools for knowledge & memory.