Mcp Memory Gateway vs Deja Vu — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mcp Memory Gateway vs Deja Vu
In-depth architectural comparison of the Mcp Memory Gateway 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
Mcp Memory Gateway
Knowledge & Memory · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Deja Vu
Knowledge & Memory · Local stdio
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mcp Memory Gateway 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 Mcp Memory Gateway 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: PreToolUse hook enforcement for AI agent tool calls, Local feedback capture and lesson storage, Auto-promotion of repeated failures into blocking rules.
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.
Pre-action gates that prevent AI coding agents from repeating known mistakes. Captures explicit feedback, auto-promotes failures into prevention rules, and enforces them via hooks.
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
Mcp Memory Gateway Tools (6)
PreToolUse hook enforcement for AI agent tool calls
Local feedback capture and lesson storage
Auto-promotion of repeated failures into blocking rules
Configurable strict enforcement mode for deny decisions
Compatibility with Claude Code, Cursor, Codex, Gemini, Amp, Cline, OpenCode
No remote server required on enforcement path
Deja Vu Tools (6)
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).
Mcp Memory Gateway is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Deja Vu belongs to Knowledge & Memory using local stdio subprocess. Select Mcp Memory Gateway when you need capabilities focused on knowledge & memory and Deja Vu when you require tools for knowledge & memory.