Memocore vs Deja Vu
A side-by-side look at the Memocore and Deja Vu MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
M
MemocoreKnowledge & Memory · Remote HTTP/SSEShared memory for all your AI agents, your whole team and every MCP client — save, search, recall.39FairAuth: oauth 2.0Verdict: choose Memocore for knowledge & memory work over a hosted endpoint; 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?
MChoose Memocore when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: OAuth 2.0.
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 have the keys it needs:
DEJA_TUI. - You want tools like
deja.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | M Memocore | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 39/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | OAuth 2.0 | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | DEJA_TUI |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 1,303 |
| Directory activity | 0 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | Not listed | 1 |
| Full listing | View Memocore | View Deja Vu |
Tools & capabilities
Memocore 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.
Memocore
{
"mcpServers": {
"memocore": {
"command": "npx",
"args": [
"-y",
"memocore"
]
}
}
}
Deja Vu
{
"mcpServers": {
"vshulcz-deja-vu": {
"command": "npx",
"args": [
"-y",
"@vshulcz/deja-vu"
],
"env": {
"DEJA_TUI": "YOUR_DEJA_TUI_HERE"
}
}
}
}
Frequently asked questions
Memocore is categorized under Knowledge & Memory and uses a remote HTTP/SSE transport. Deja Vu belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Memocore 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.
Memocore has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 memocore and vshulcz-deja-vu as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Memocore has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Deja Vu has 65/100 (Great) with 8 views, 0 installs and 1,303 GitHub stars.