MemoFS MCP Server vs Deja Vu
A side-by-side look at the MemoFS MCP Server and Deja Vu MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MemoFS MCP Server for knowledge & memory work as a local process; choose Deja Vu 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 MemoFS MCP Server when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 43/100 · Fair | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | 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 | 6 | 1,209 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View MemoFS MCP Server | View Deja Vu |
Tools & capabilities
MemoFS MCP Server 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.
MemoFS MCP Server
{
"mcpServers": {
"memofs-mcp-server": {
"command": "npx",
"args": [
"-y",
"@memofs/cli"
]
}
}
}
Deja Vu
{
"mcpServers": {
"vshulcz-deja-vu": {
"command": "npx",
"args": [
"-y",
"@vshulcz/deja-vu"
]
}
}
}
Frequently asked questions
MemoFS MCP Server is categorized under Knowledge & Memory and uses a local stdio subprocess. Deja Vu belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MemoFS MCP Server for knowledge & memory work and Deja Vu 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.
MemoFS MCP Server 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 memofs-mcp-server and vshulcz-deja-vu as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MemoFS MCP Server has a quality signal of 43/100 (Fair) with 0 views, 0 installs and 6 GitHub stars. Deja Vu has 69/100 (Great) with 2 views, 0 installs and 1,209 GitHub stars.