What is the key difference between Vault Cortex and MCP Obsidian Via Rest?

Vault Cortex belongs to the Knowledge & Memory category with local stdio execution, while MCP Obsidian Via Rest belongs to the Knowledge & Memory category with local stdio execution.

How do I install Vault Cortex or MCP Obsidian Via Rest in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Vault Cortex and MCP Obsidian Via Rest free or paid?

Vault Cortex operates under a Free / Open Source model (OAuth 2.0). MCP Obsidian Via Rest operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Vault Cortex lists 6 tools with 2 views and 24 GitHub stars. MCP Obsidian Via Rest lists 6 tools with 1 views and 13 GitHub stars.

Can I use both Vault Cortex and MCP Obsidian Via Rest together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Vault Cortex vs MCP Obsidian Via Rest

In-depth architectural comparison of the Vault Cortex and MCP Obsidian Via Rest 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

Vault Cortex

Knowledge & Memory · Local stdio

Quality: 47/100 (Fair) | Auth: OAuth 2.0

MCP Obsidian Via Rest

Knowledge & Memory · Local stdio

Quality: 40/100 (Fair) | Auth: No auth required

Verdict Summary: Choose Vault Cortex if you need specialized Knowledge & Memory tools running via a local process. Choose MCP Obsidian Via Rest 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 Vault Cortex when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: MCP_AUTH_TOKEN, VAULT_PATH.
Primary tools included: Hybrid FTS5 and vector search, Cross-encoder search reranking, Obsidian note and file read/write access.

Explore Vault Cortex Details

Choose MCP Obsidian Via Rest 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: API_KEY, API_URLS, DEBUG, MCP_HTTP_PATH, OBSIDIAN_API_KEY.

Feature & Specification Comparison

Specification	Vault Cortex aliasunder Knowledge & Memory	MCP Obsidian Via Rest Knowledge & Memory
Summary	MCP server for Obsidian vaults — hybrid search, notes & files, memory, tasks, link graph, OAuth-protected.	MCP Server for Obsidian Vault Access via Local REST API
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

Vault Cortex Tools (6)

Hybrid FTS5 and vector search

Cross-encoder search reranking

Obsidian note and file read/write access

Structured memory with dated entries

Kanban-aware task management

OAuth 2.1 remote access

MCP Obsidian Via Rest Tools (6)

Retrieve note content and metadata

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

Vault Cortex Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "aliasunder-vault-cortex": {
      "command": "npx",
      "args": [
        "-y",
        "vault-cortex@latest"
      ],
      "env": {
        "MCP_AUTH_TOKEN": "YOUR_MCP_AUTH_TOKEN_HERE",
        "VAULT_PATH": "YOUR_VAULT_PATH_HERE"
      }
    }
  }
}

MCP Obsidian Via Rest Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mcp-obsidian-via-rest": {
      "command": "bunx",
      "args": [
        "-y",
        "@oleksandrkucherenko/mcp-obsidian"
      ],
      "env": {
        "API_KEY": "YOUR_API_KEY_HERE",
        "API_URLS": "YOUR_API_URLS_HERE",
        "DEBUG": "YOUR_DEBUG_HERE",
        "MCP_HTTP_PATH": "YOUR_MCP_HTTP_PATH_HERE",
        "OBSIDIAN_API_KEY": "YOUR_OBSIDIAN_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

Vault Cortex is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, MCP Obsidian Via Rest belongs to Knowledge & Memory using local stdio subprocess. Select Vault Cortex when you need capabilities focused on knowledge & memory and MCP Obsidian Via Rest when you require tools for knowledge & memory.

More alternatives to Vault Cortex More alternatives to MCP Obsidian Via Rest Knowledge & Memory category hub