Directory vs Deja Vu — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Directory vs Deja Vu
In-depth architectural comparison of the Directory and Deja Vu 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
Directory
Knowledge & Memory · Local stdio
Quality: 36/100 (Fair) | Auth: No auth required
Deja Vu
Knowledge & Memory · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Verdict Summary: Choose Directory if you need specialized Knowledge & Memory tools running via a local process. Choose Deja Vu 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 Directory 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: Four independent memory layers so one layer's failure doesn't cascade, Local-LLM memory service (Qwen 3.5 9B via Ollama) for truth extraction and indexing, Qdrant vector database plus Mem0 for semantic memory.
Discover and query every business on ANOTS — search, ask, or find-and-ask over MCP.
Local memory layer over the session histories coding agents already write (Claude Code, Codex CLI, opencode): lexical search, recall tools, session-start auto-recall, secret redaction at index time, cross-machine sync over SSH.
Directory is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Deja Vu belongs to Knowledge & Memory using local stdio subprocess. Select Directory when you need capabilities focused on knowledge & memory and Deja Vu when you require tools for knowledge & memory.