Claude Find vs Workspace Qdrant MCP

In-depth architectural comparison of the Claude Find and Workspace Qdrant MCP 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 Workspace Qdrant 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).
• You have access to required keys: QDRANT_URL.
• Primary tools included: search, retrieve, rules.

Feature & Specification Comparison

Specification	Claude Find Cavinooo Knowledge & Memory	Workspace Qdrant MCP ChrisGVE Knowledge & Memory
Summary	Pull Deep Memory from across your Claude Code Sessions — when you need it.	Project-scoped semantic workspace memory for AI coding assistants. Watches your project files, auto-indexes code and docs into Qdrant with tree-sitter semantic chunking, LSP integration, and hybrid search (dense + sparse + RRF). 6 MCP tools: store, search, retrieve, grep, list, rules. Alpha — testers and feedback welcome.
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": {
    "chrisgve-workspace-qdrant-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "chrisgve-workspace-qdrant-mcp"
      ],
      "env": {
        "QDRANT_URL": "YOUR_QDRANT_URL_HERE"
      }
    }
  }
}

Related MCP Server Comparisons