Conventions MCP vs Deja Vu — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Conventions MCP vs Deja Vu
In-depth architectural comparison of the Conventions MCP 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
Conventions MCP
Knowledge & Memory · Local stdio
Quality: 45/100 (Fair) | Auth: No auth required
Deja Vu
Knowledge & Memory · Local stdio
Quality: 56/100 (Good) | Auth: No auth required
Verdict Summary: Choose Conventions MCP 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?
C
Choose Conventions MCP 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: 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.
Memory for coding conventions and standing instructions that persists across sessions.
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.
Conventions MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Deja Vu belongs to Knowledge & Memory using local stdio subprocess. Select Conventions MCP when you need capabilities focused on knowledge & memory and Deja Vu when you require tools for knowledge & memory.