Robo Cortex vs Deja Vu — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Robo Cortex vs Deja Vu
In-depth architectural comparison of the Robo Cortex 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
Robo Cortex
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Deja Vu
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Robo Cortex 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 Robo Cortex 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: Git blob hash-based drift detection, Local SQLite storage with FTS5 search, Evidence-backed memory lifecycle.
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: Zero-dependency single binary, fully local operation, Search 3.5 GB of session history in ~1.5 ms, Supports multiple coding agents via MCP protocol.
Git-aware, evidence-based memory store for AI coding agents. Memories anchored to git blob hashes are automatically flagged for review when linked code changes. pip install robo-cortex[mcp] or on registry.modelcontextprotocol.io
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
Robo Cortex Tools (6)
Git blob hash-based drift detection
Local SQLite storage with FTS5 search
Evidence-backed memory lifecycle
Automatic needs_review status for changed code
Audit trail for status changes
No embeddings, network calls, or API keys by default
Deja Vu Tools (6)
Zero-dependency single binary, fully local operation
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).
Robo Cortex is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Deja Vu belongs to Knowledge & Memory using local stdio subprocess. Select Robo Cortex when you need capabilities focused on knowledge & memory and Deja Vu when you require tools for knowledge & memory.