Lore vs Claude Find — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Lore vs Claude Find
In-depth architectural comparison of the Lore and Claude Find 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
Lore
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Claude Find
Knowledge & Memory · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Lore if you need specialized Knowledge & Memory tools running via a local process. Choose Claude Find 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 Lore 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: LORE_DIR, LORE_DB, CLAUDE_PROJECTS_DIR.
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.
Lore is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Claude Find belongs to Knowledge & Memory using local stdio subprocess. Select Lore when you need capabilities focused on knowledge & memory and Claude Find when you require tools for knowledge & memory.