Deja Vu vs Statelessagent — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Deja Vu vs Statelessagent
In-depth architectural comparison of the Deja Vu and Statelessagent 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
Statelessagent
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: API Key required
Verdict Summary: Choose Deja Vu if you need specialized Knowledge & Memory tools running via a local process. Choose Statelessagent 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).
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
Primary tools included: Provenance tracking and stale knowledge detection, Dual-layer memory with atomic fact extraction, 19 MCP tools for session handoffs, decisions, and search.
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.
Memory with provenance tracking — records where agent knowledge originated and detects when sources change. 17 MCP tools for session handoffs, decisions, semantic search, and knowledge graph. Works across Claude Code, Cursor, Windsurf, Codex CLI, and Gemini CLI. Single Go binary, SQLite + vector search, fully local.
Category & Scope
Tools & Capabilities Breakdown
Deja Vu Tools (1)
deja
Depends on the mode, below.
Statelessagent Tools (6)
Provenance tracking and stale knowledge detection
Dual-layer memory with atomic fact extraction
19 MCP tools for session handoffs, decisions, and search
Local SQLite and vector search with optional semantic upgrade
PII scanning and push protection for team safety
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, Statelessagent belongs to Knowledge & Memory using local stdio subprocess. Select Deja Vu when you need capabilities focused on knowledge & memory and Statelessagent when you require tools for knowledge & memory.