What is the key difference between Enquire MCP and Vault Cortex?

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

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

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

Which MCP server has more tools and community activity?

Enquire MCP lists 6 tools with 2 views and 33 GitHub stars. Vault Cortex lists 6 tools with 2 views and 19 GitHub stars.

Can I use both Enquire MCP and Vault Cortex 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

Enquire MCP vs Vault Cortex

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

Enquire MCP

Knowledge & Memory · Local stdio

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

Vault Cortex

Knowledge & Memory · Local stdio

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

Verdict Summary: Choose Enquire MCP if you need specialized Knowledge & Memory tools running via a local process. Choose Vault Cortex 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 Enquire MCP 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: Hybrid retrieval: BM25, ML embeddings, BGE reranker with RRF fusion, Supports Markdown, PDFs with Tesseract OCR, Canvas, Dataview, and Bases, Returns source paths, page citations, age_days, and stale flags.

Explore Enquire MCP Details

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.

Feature & Specification Comparison

Specification	Enquire MCP oomkapwn Knowledge & Memory	Vault Cortex aliasunder Knowledge & Memory
Summary	Long-term memory for AI agents (Claude Code/Desktop, Cursor, ChatGPT, Codex, OpenClaw) backed by a local Obsidian markdown vault. Hybrid retrieval (BM25 + ML embeddings + BGE reranker, RRF-fused), HNSW + int8 quantization, agentic RAG (HyDE + sub-question), GraphRAG-light (Louvain wikilink community detection), standalone Obsidian Bases, PDFs + Tesseract OCR. 46 tools, 19 MCP prompts, MIT, SLSA L2, zero cloud calls during serve. npx -y @oomkapwn/enquire-mcp serve --vault	MCP server for Obsidian vaults — hybrid search, notes & files, memory, tasks, link graph, OAuth-protected.
Category & Scope

Tools & Capabilities Breakdown

Enquire MCP Tools (6)

Hybrid retrieval: BM25, ML embeddings, BGE reranker with RRF fusion

Supports Markdown, PDFs with Tesseract OCR, Canvas, Dataview, and Bases

Returns source paths, page citations, age_days, and stale flags

Read-only by default with optional write tools behind a flag

Zero outbound network calls during serving

Agent-agnostic, vendor-neutral MCP server

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

Enquire MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "oomkapwn-enquire-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@oomkapwn/enquire-mcp"
      ]
    }
  }
}

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

Frequently Asked Questions

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

More alternatives to Enquire MCP More alternatives to Vault Cortex Knowledge & Memory category hub Canonical compare URL