What is the main functional difference between Codeagent Memory and Deja Vu?

Codeagent Memory is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Deja Vu belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Codeagent Memory for knowledge & memory work and Deja Vu for knowledge & memory.

How do I install Codeagent Memory or Deja Vu in Claude Desktop, Cursor, or Windsurf?

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Codeagent Memory has no confirmed install command yet — follow its own setup instructions.

Are Codeagent Memory and Deja Vu free to use, or do they require API keys?

Codeagent Memory has no declared pricing — check the project's own site. Deja Vu is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Can I run both Codeagent Memory and Deja Vu at the same time in my AI client?

Yes. MCP clients support multiple servers: add codeagent-memory and vshulcz-deja-vu as separate keys in the same mcpServers object, and your assistant will call tools from either one.

Which MCP server has higher directory engagement and quality ratings?

On AllMCPs, Codeagent Memory has a quality signal of 33/100 (Emerging) with 0 views, 0 installs and 1 GitHub stars. Deja Vu has 69/100 (Great) with 2 views, 0 installs and 1,146 GitHub stars.

Codeagent Memory vs Deja Vu

A side-by-side look at the Codeagent Memory and Deja Vu MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Codeagent MemoryKnowledge & MemoryLocal code graph and solution memory for coding agents via CLI and MCP.33EmergingAuth: not declared

Deja VuKnowledge & Memory · Local subprocess (stdio)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.69GreatAuth: no auth required

Verdict: choose Codeagent Memory for knowledge & memory work; choose Deja Vu for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.

Spec	C Codeagent Memory	Deja Vu
Category	Knowledge & Memory	Knowledge & Memory
Quality signal	33/100 · Emerging	69/100 · Great
Install command	Not confirmed yet	Confirmed
Transport	—	Local subprocess (stdio)
Auth	Not declared	No auth required
Pricing	Not declared	Free
Required env vars	None listed	None listed
Verified owner	Community listing	Community listing
GitHub stars	1	1,146
Directory activity	0 views 0 installs 0 upvotes	2 views 0 installs 0 upvotes
Tools	Not listed	1
Full listing	View Codeagent Memory	View Deja Vu

Codeagent Memory vs Deja Vu

Which MCP server should you choose?

C
Choose Codeagent Memory when

Choose Deja Vu when

Feature & specification comparison

Tools & capabilities

Codeagent Memory tools

Deja Vu tools 1

Ready-to-paste client configs