Central Intelligence vs Deja Vu — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Central Intelligence vs Deja Vu
In-depth architectural comparison of the Central Intelligence 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
Central Intelligence
Knowledge & Memory · Local stdio
Quality: 48/100 (Fair) | Auth: API Key required
Deja Vu
Knowledge & Memory · Local stdio
Quality: 69/100 (Great) | Auth: No auth required
Verdict Summary: Choose Central Intelligence 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 Central Intelligence when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: CI_API_KEY.
Primary tools included: Five MCP memory tools, Semantic search with scoped memories, Agent, user, and organization visibility.
Persistent memory for AI agents. Five tools (remember, recall, context, forget, share) with semantic search via vector embeddings and agent/user/org scoping. Works with Claude Code, Cursor, Windsurf, and any MCP client.
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
Central Intelligence Tools (6)
Five MCP memory tools
Semantic search with scoped memories
Agent, user, and organization visibility
Cross-tool configuration-file search
Local dashboard and memory synchronization
Memory import and export
Deja Vu Tools (1)
deja
Depends on the mode, below.
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).
Central Intelligence is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Deja Vu belongs to Knowledge & Memory using local stdio subprocess. Select Central Intelligence when you need capabilities focused on knowledge & memory and Deja Vu when you require tools for knowledge & memory.