Deja Vu MCP server
io.github.vshulcz/deja-vu·v0.23.5·1.1k starsdeja-vu: local memory over the session histories of forty-three coding agents.
not scanned yet
1.1k stars1.5k downloads/wk
Reviews
Write oneNobody has reviewed Deja Vu yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Deja Vu tools
No tool declarations could be read from the package source. They show once the server is installed.
How Deja Vu compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 95% of 48,255 servers
- GitHub stars
- 1,120
- more than 95% of 28,688 servers
- Downloads a week
- 1,493
- more than 95% of 12,191 servers with a package
Release history: 16 versions in the registry since 2026-09-15, latest 2026-11-03, typically one every 3 days.
Install Deja Vu in Claude Code, Cursor or VS Code
Runs npx -y @vshulcz/deja-vu on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add deja-vu -- npx -y @vshulcz/deja-vu
What the publisher says
From the Deja Vu repository's README, as published. We do not edit it. Read it on GitHub
The one memory your coding agents share, built from the history already on your disk.
Your agent is about to re-debug something you fixed in March — in a different agent. deja indexes the sessions Claude Code, Codex, Cursor and every other agent on this machine already wrote to disk, and hands the right one back in whichever agent asks.
Nobody searched anything — the agent called deja itself. Every line is quoted from two real sessions.
Every memory tool starts empty and records forward. deja starts full.
And nobody has to ask for it: recall arrives at session start, on every prompt, before a file is edited or a command runs, and after one fails. Keys and tokens are stripped as the index is built, so what reaches the model is safe to send.
85.3% hit@1 on LongMemEval-S · 69.7% retrieval hit@1 on LoCoMo · millisecond lookups over gigabytes of history Both harnesses ship in this repo and run on the public datasets in minutes · check the numbers yourself
English | 中文
Docs · Benchmarks · How it compares · Building it into your tool Found it useful? Star deja-vu on GitHub so other developers can find it.
Install
curl -fsSL https://raw.githubusercontent.com/vshulcz/deja-vu/main/install.sh | sh
deja install --autoTen seconds to install, about ten to index, and it is useful. The second command wires MCP recall into every agent it finds, turns on session-start recall where the agent supports it, and builds the first index so the next session does not pay for it.
Start a new agent session and ask it something you worked on months ago:
have we dealt with jwt refresh rotation before? check your memory
It does not have to be asked, either — with auto-recall the agent already knows what you solved in that project when the session opens.
Other ways to install, and what to do if you want less than all of it
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Deja Vu: common questions
- Is Deja Vu MCP server safe?
- Yes, by our scan: it is graded A (92/100). Read the Deja Vu safety report
- How do I install Deja Vu?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Deja Vu need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Deja Vu maintained?
- The last commit was 32 days ago (2026-10-02). The latest release is v0.23.5.
- How does Deja Vu compare with other MCP servers?
- safety score 92/100 (higher than 95% of 48,255 servers); github stars 1,120 (more than 95% of 28,688 servers); downloads a week 1,493 (more than 95% of 12,191 servers with a package). Full comparison.