What is the key difference between Vault Cortex and Engram Rs?

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

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

Vault Cortex operates under a Free / Open Source model (OAuth 2.0). Engram Rs operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Vault Cortex lists 6 tools with 2 views and 19 GitHub stars. Engram Rs lists 16 tools with 2 views and 27 GitHub stars.

Can I use both Vault Cortex and Engram Rs 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 Engram Rs

In-depth architectural comparison of the Vault Cortex and Engram Rs 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: 44/100 (Fair) | Auth: OAuth 2.0

Engram Rs

Knowledge & Memory · Local stdio

Quality: 57/100 (Good) | Auth: API Key required

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

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).

Feature & Specification Comparison

Specification	Vault Cortex aliasunder Knowledge & Memory	Engram Rs kael-bit Knowledge & Memory
Summary
Category & Scope	Knowledge & Memory	Knowledge & Memory

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

Engram Rs Tools (16)

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": {
        "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"
      }
    }
  }
}

Engram Rs Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "kael-bit-engram-rs": {
      "command": "npx",
      "args": [
        "-y",
        "engram-rs-mcp"
      ],
      "env": {
        "ENGRAM_EMBEDDING_PROVIDER": "YOUR_ENGRAM_EMBEDDING_PROVIDER_HERE",
        "ENGRAM_EMBEDDING_API_KEY": "YOUR_ENGRAM_EMBEDDING_API_KEY_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Vault Cortex More alternatives to Engram Rs Knowledge & Memory category hub