Deja Vu vs Agent Memory
A side-by-side look at the Deja Vu and Agent Memory MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Deja Vu for knowledge & memory work as a local process; choose Agent Memory for knowledge & memory as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Deja Vu when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
deja.
Choose Agent Memory when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
memory.fetch_context, memory.propose_update, memory.status.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 69/100 · Great | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,209 | 12 |
| Directory activity | 2 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 1 | 3 |
| Full listing | View Deja Vu | View Agent Memory |
Tools & capabilities
Deja Vu tools 1
dejaDepends on the mode, below.
Agent Memory tools 3
memory.fetch_contextRead a budgeted Markdown context pack.memory.propose_updateSubmit structured edits (apply or stage).memory.statusReport memory health: file counts, staged proposals (with drift), security/git/lock posture.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Deja Vu
{
"mcpServers": {
"vshulcz-deja-vu": {
"command": "npx",
"args": [
"-y",
"@vshulcz/deja-vu"
]
}
}
}
Agent Memory
{
"mcpServers": {
"xchucx-agent-memory": {
"command": "npx",
"args": [
"-y",
"@xchucx/agent-memory"
]
}
}
}
Frequently asked questions
Deja Vu is categorized under Knowledge & Memory and uses a local stdio subprocess. Agent Memory belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Deja Vu for knowledge & memory work and Agent Memory for knowledge & memory.
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.
Deja Vu is listed as free. Auth: no auth required. Agent Memory 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.
Yes. MCP clients support multiple servers: add vshulcz-deja-vu and xchucx-agent-memory as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Deja Vu has a quality signal of 69/100 (Great) with 2 views, 0 installs and 1,209 GitHub stars. Agent Memory has 60/100 (Good) with 4 views, 0 installs and 12 GitHub stars.