Deja Vu vs Zotero Library MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Deja Vu vs Zotero Library MCP
In-depth architectural comparison of the Deja Vu and Zotero Library 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
Zotero Library MCP
Knowledge & Memory · Local stdio
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Deja Vu if you need specialized Knowledge & Memory tools running via a local process. Choose Zotero Library 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.
Add papers and books to Zotero by DOI, arXiv ID, or ISBN and manage your library
Deja Vu is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Zotero Library MCP belongs to Knowledge & Memory using local stdio subprocess. Select Deja Vu when you need capabilities focused on knowledge & memory and Zotero Library MCP when you require tools for knowledge & memory.