Deja Vu vs Penfield MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Deja Vu vs Penfield MCP
In-depth architectural comparison of the Deja Vu and Penfield MCP 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
Penfield MCP
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: OAuth 2.0
Verdict Summary: Choose Deja Vu if you need specialized Knowledge & Memory tools running via a local process. Choose Penfield MCP 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.
Penfield: persistent memory with hybrid search (BM25 + vector + graph), 24 relationship types for knowledge graphs, context checkpoints for cognitive handoff, artifact storage, and personality system. Works across Claude, Cursor, Windsurf, and any MCP client.
Category & Scope
Tools & Capabilities Breakdown
Deja Vu Tools (1)
deja
Depends on the mode, below.
Penfield MCP Tools (6)
Persistent memory across sessions
Hybrid BM25, vector, and graph search
Knowledge graph with 24 relationship types
Context save and restore checkpoints
Artifact storage and retrieval
OAuth-authenticated hosted MCP endpoint
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, Penfield MCP belongs to Knowledge & Memory using local stdio subprocess. Select Deja Vu when you need capabilities focused on knowledge & memory and Penfield MCP when you require tools for knowledge & memory.