MCP Obsidian vs Cortex Plugin — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Obsidian vs Cortex Plugin
In-depth architectural comparison of the MCP Obsidian and Cortex Plugin 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: 61/100 (Good) | Auth: No auth required
Cortex Plugin
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 Cortex Plugin 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: 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.
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: MEMEM_TELEMETRY_SOURCE.
Primary tools included: Event-triggered background miner extracting durable lessons from conversations, Stores memories as markdown files in a local Obsidian vault, Active Memory Slice assembling query-tailored context briefings.
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.
Persistent, self-evolving memory plugin for Claude Code. Background miner extracts durable lessons (decisions, conventions, bug fixes) from completed sessions via Claude Haiku, stores them as human-readable markdown in an Obsidian vault, and assembles query-tailored context briefings at session start. Local-first, no cloud, no API keys. Self-healing install via uv bootstrap shim, /cortex-doctor preflight, graceful FTS-only degraded mode when claude CLI missing. MIT.
Tools & Capabilities Breakdown
MCP Obsidian Tools (6)
Local stdio MCP access to an Obsidian vault
Note reading, writing, patching, moving, and deletion
Multi-word search with BM25 reranking
Frontmatter and tag management
Vault statistics, directory listing, and batch reads
Read-only mode and vault-root path restrictions
Cortex Plugin Tools (6)
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, Cortex Plugin belongs to Knowledge & Memory using local stdio subprocess. Select MCP Obsidian when you need capabilities focused on knowledge & memory and Cortex Plugin when you require tools for knowledge & memory.