Obsidian MCP Server vs Cortex Plugin

In-depth architectural comparison of the Obsidian MCP Server 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.

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).
• You have access to required keys: VAULT_PATH.
• Primary tools included: read-note, read-multiple-notes, create-note.

Explore Obsidian MCP Server Details

Choose Cortex Plugin 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: MEMEM_TELEMETRY_SOURCE.
• Primary tools included: .

Feature & Specification Comparison

Specification	Obsidian MCP Server smith-and-web Knowledge & Memory	Cortex Plugin TT-Wang Knowledge & Memory
Summary	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.	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

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).

{
  "mcpServers": {
    "smith-and-web-obsidian-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@smith-and-web/obsidian-mcp-server"
      ],
      "env": {
        "VAULT_PATH": "YOUR_VAULT_PATH_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "tt-wang-cortex-plugin": {
      "command": "pipx",
      "args": [
        "install",
        "memem"
      ],
      "env": {
        "MEMEM_TELEMETRY_SOURCE": "YOUR_MEMEM_TELEMETRY_SOURCE_HERE"
      }
    }
  }
}

Related MCP Server Comparisons