Log inSubmit server

Anamnese vs Deja Vu

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

A
AnamneseKnowledge & MemoryA self-improving memory layer. Your memory, notes, tasks and goals, remembered everywhere.37FairAuth: not declaredDeja Vu logoDeja VuKnowledge & MemoryLocal 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.59GoodAuth: no auth required

Verdict: choose Anamnese for knowledge & memory work; choose Deja Vu for knowledge & memory. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

A
Choose Anamnese when

  • You need dedicated capabilities in the Knowledge & Memory domain.
Explore Anamnese

Deja Vu logoChoose Deja Vu when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • Its auth model fits you: No auth required.
  • You want tools like deja.
Explore Deja Vu

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
Anamnese		Deja Vu logoDeja Vu
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal37/100 · Fair59/100 · Good
Install commandNot confirmed yetNot confirmed yet
Transport——
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—1,287
Directory activity 0 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
ToolsNot listed1
Full listingView Anamnese View Deja Vu

Tools & capabilities

Anamnese tools

No tool names declared yet. Check the project README from the listing page.

Deja Vu tools 1

  • dejaDepends on the mode, below.

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.

Anamnese

No confirmed install command for Anamnese yet — follow the setup steps linked from its listing page rather than a guessed package name.

Deja Vu

No confirmed install command for Deja Vu yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

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

Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.

Anamnese 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.

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

On AllMCPs, Anamnese has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Deja Vu has 59/100 (Good) with 7 views, 0 installs and 1,287 GitHub stars.

Popular comparisons with Anamnese

Popular comparisons with Deja Vu