Claude Find vs Cortex Plugin

In-depth architectural comparison of the Claude Find 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 Claude Find 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: Indexes raw JSONL session transcripts from Claude Code, Uses GPU-accelerated qwen3 embeddings via Ollama, Hybrid semantic and keyword search with Reciprocal Rank Fusion.

Explore Claude Find 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: Event-triggered background miner extracting durable lessons from conversations, Stores memories as markdown files in a local Obsidian vault, Active Memory Slice assembling query-tailored context briefings.

Feature & Specification Comparison

Specification	Claude Find Cavinooo Knowledge & Memory	Cortex Plugin TT-Wang Knowledge & Memory
Summary	Pull Deep Memory from across your Claude Code Sessions — when you need it.	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

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": {
    "cavinooo-claude-find": {
      "command": "bunx",
      "args": [
        "claude-find"
      ]
    }
  }
}

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

Related MCP Server Comparisons