What is the key difference between Vault Cortex and Cortex Plugin?

Vault Cortex belongs to the Knowledge & Memory category with local stdio execution, while Cortex Plugin belongs to the Knowledge & Memory category with local stdio execution.

How do I install Vault Cortex or Cortex Plugin 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 Cortex Plugin free or paid?

Vault Cortex operates under a Free / Open Source model (OAuth 2.0). Cortex Plugin 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 15 GitHub stars. Cortex Plugin lists 6 tools with 1 views and 31 GitHub stars.

Can I use both Vault Cortex and Cortex Plugin 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.

How do I install Vault Cortex or Cortex Plugin in Claude Desktop, Cursor, or Windsurf?

Both servers follow the standard Model Context Protocol configuration format. Simply copy the JSON block from the configuration section above and paste it into your AI client's mcpServers configuration object (for instance in claude_desktop_config.json or ~/.cursor/mcp.json ), then completely restart or refresh the application.

Are Vault Cortex and Cortex Plugin free to use, or do they require API keys?

Vault Cortex is listed under a Free / Open Source model with OAuth 2.0 . Cortex Plugin operates under a Free / Open Source model with No auth required . If environment variables are required (such as API keys), be sure to define them under the env key in your MCP client's configuration file.

Can I run both Vault Cortex and Cortex Plugin at the same time in my AI client?

Yes! MCP clients support multi-server orchestration. You can include both aliasunder-vault-cortex and tt-wang-cortex-plugin as distinct keys inside the single mcpServers object in your configuration file. Your AI assistant will automatically select and call the appropriate tool from either server during chat sessions.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Vault Cortex has a Quality Score of 36 /100 ( Fair ) with 2 views, 0 installs, and 15 GitHub stars. Cortex Plugin holds a Quality Score of 55 /100 ( Good ) with 1 views, 0 installs, and 31 GitHub stars.

Side-by-Side Model Context Protocol Comparison

Vault Cortex vs Cortex Plugin

In-depth architectural comparison of the Vault Cortex 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

Vault Cortex

Knowledge & Memory · Local stdio

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

Cortex Plugin

Knowledge & Memory · Local stdio

Quality: 55/100 (Good) | Auth: No auth required

Verdict Summary: Choose Vault Cortex 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 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: VAULT_CORTEX_OAUTH_CLIENT_ID, VAULT_CORTEX_OAUTH_CLIENT_SECRET, VAULT_CORTEX_VAULT_PATH, VAULT_CORTEX_SERVER_PORT.
Primary tools included: Hybrid search using FTS5 keyword matching and vector similarity with reranking, Structured, append-only memory with topic recall and history, Kanban-aware task queries and updates supporting Tasks plugin and Dataview formats.

Explore Vault Cortex 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).

Feature & Specification Comparison

Specification	Vault Cortex aliasunder Knowledge & Memory	Cortex Plugin TT-Wang Knowledge & Memory
Summary	MCP server for Obsidian vaults — hybrid search, notes & files, memory, tasks, link graph, OAuth-protected.	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.
Category & Scope

Tools & Capabilities Breakdown

Vault Cortex Tools (6)

Hybrid search using FTS5 keyword matching and vector similarity with reranking

Structured, append-only memory with topic recall and history

Kanban-aware task queries and updates supporting Tasks plugin and Dataview formats

Read and render non-markdown files including images, PDFs, and canvases

Obsidian-native support for frontmatter, wikilinks, tags, headings, and daily notes

OAuth 2.1 authentication for secure remote access

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",
        "aliasunder-vault-cortex"
      ],
      "env": {
        "VAULT_CORTEX_OAUTH_CLIENT_ID": "YOUR_VAULT_CORTEX_OAUTH_CLIENT_ID_HERE",
        "VAULT_CORTEX_OAUTH_CLIENT_SECRET": "YOUR_VAULT_CORTEX_OAUTH_CLIENT_SECRET_HERE",
        "VAULT_CORTEX_VAULT_PATH": "YOUR_VAULT_CORTEX_VAULT_PATH_HERE",
        "VAULT_CORTEX_SERVER_PORT": "YOUR_VAULT_CORTEX_SERVER_PORT_HERE"
      }
    }
  }
}

Cortex Plugin Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

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

More alternatives to Vault Cortex More alternatives to Cortex Plugin Knowledge & Memory category hub