In-depth architectural comparison of the Sage 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
Sage
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: other
Deja Vu
Knowledge & Memory · Local stdio
Quality: 69/100 (Great) | Auth: No auth required
Verdict Summary: Choose Sage 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 Sage when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: other (Free / Open Source).
You have access to required keys: SAGE_PROVIDER, SAGE_PROJECT, SAGE_IDENTITY_PATH.
Institutional memory for AI agents with real BFT consensus. 4 application validators vote on every memory before it's committed — no more storing garbage. 13 MCP tools, runs locally, works with any MCP-compatible model. Backed by 4 published research papers.
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.
Category & Scope
Tools & Capabilities Breakdown
Sage Tools (6)
Consensus-validated persistent memory
Semantic recall with confidence scores
Durable agent-assigned tasks
Unified inbox and reply workflows
Access controls and bounded federation
Local dashboard and recovery snapshots
Deja Vu Tools (1)
deja
Depends on the mode, below.
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).
Sage is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Deja Vu belongs to Knowledge & Memory using local stdio subprocess. Select Sage when you need capabilities focused on knowledge & memory and Deja Vu when you require tools for knowledge & memory.