deja-vu MCP server

Coding agent memory for Claude Code, Codex, Cursor and 39 more, built from the session history already on your disk. Local search, MCP and hooks, no LLM, one Go binary.

What deja-vu does

Summarised from the project README; check the repository for the latest details.

Features

• Starts full. Months of history from before you installed it are searchable on day one: `deja "connection pool exhausted"` over gigabytes.
• One memory, every agent. A fix found in Codex comes back in Claude Code, Cursor or opencode; all forty-two agents read the same index.
• Nobody has to ask. Recall arrives at session start, before a file is edited or a command runs, and after a command fails.
• Survives compaction. Over 43 measured compactions the summary kept 77% of the decisions and 0.2% of the commands; deja hands back the rest (how).
• Indexes the work, not just the talk. The files each turn opened, the commands with their exit status, the exact spans an edit replaced.
• Knows what held. `deja promote --state rejected` marks a reverted decision, and every later hit says it was tried and why it was dropped; `--state accepted` takes the mark back.

Tools exposed (10)

• deja – `mode`, `q`, `harness?`, `project?`, `limit?`
• Mode – `q` is
• recall – the question, or an exact error string, name or flag
• context – the same as recall
• blame – a file path
• fix – the failing output, verbatim
• how – the tool or target, e.g. `go test`
• orient – nothing — it asks about the project
• remember – one durable fact or decision
• handoff – a session id or harness name; empty for the newest session here

How to install deja-vu

Featured in: Best MCP servers for long-term memory · Best MCP servers for LM Studio

Listed on Socketlist – add this badge to your README:

Badge markdown[](https://socketlist.pages.dev/s/vshulcz-deja-vu/)

Maintain this project? Get it featured for free during launch →

Compare with ruflo →

Related Memory & Knowledge MCP servers