Deja Vu vs Recallnest — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Deja Vu vs Recallnest
In-depth architectural comparison of the Deja Vu and Recallnest 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
Deja Vu
Knowledge & Memory · Local stdio
Quality: 68/100 (Great) | Auth: No auth required
Recallnest
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Verdict Summary: Choose Deja Vu if you need specialized Knowledge & Memory tools running via a local process. Choose Recallnest 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 Deja Vu 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).
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.
Persistent memory MCP server for AI coding agents (Claude Code, Codex, Gemini CLI). Hybrid retrieval (vector + BM25), cross-encoder reranking, knowledge graph with PPR traversal, session checkpoint/resume, and multi-scope isolation. Local-first with LanceDB + SQLite, zero external dependencies.
Category & Scope
Tools & Capabilities Breakdown
Deja Vu Tools (1)
deja
Depends on the mode, below.
Recallnest Tools (6)
Hybrid retrieval: vector, BM25, multi-vector levels, and knowledge graph PPR
Session checkpoint and resume with repo-state guarding
Multi-scope isolation with related scope sidecar search
Memory lifecycle management: decay, consolidation, promotion, and archival
Privacy tiers with cascade forgetting and write-time admission control
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).
Deja Vu is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Recallnest belongs to Knowledge & Memory using local stdio subprocess. Select Deja Vu when you need capabilities focused on knowledge & memory and Recallnest when you require tools for knowledge & memory.