Deja Vu vs Yempik Company Brain
A side-by-side look at the Deja Vu and Yempik Company Brain MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Y
Yempik Company BrainKnowledge & Memory · Remote HTTP/SSEGoverned company memory: search decisions, rules and client facts; propose updates for review.39FairAuth: oauth 2.0Verdict: choose Deja Vu for knowledge & memory work as a local process; choose Yempik Company Brain for knowledge & memory over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
YChoose Yempik Company Brain 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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | Y Yempik Company Brain | |
|---|---|---|
| Category | Knowledge & Memory | Knowledge & Memory |
| Quality signal | 65/100 · Great | 39/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | No auth required | OAuth 2.0 |
| Pricing | Free | Not declared |
| Required env vars | DEJA_TUI | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1,303 | — |
| Directory activity | 8 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 1 | Not listed |
| Full listing | View Deja Vu | View Yempik Company Brain |
Tools & capabilities
Deja Vu tools 1
dejaDepends on the mode, below.
Yempik Company Brain tools
No tool names declared yet. Check the project README from the listing page.
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.
Deja Vu
{
"mcpServers": {
"vshulcz-deja-vu": {
"command": "npx",
"args": [
"-y",
"@vshulcz/deja-vu"
],
"env": {
"DEJA_TUI": "YOUR_DEJA_TUI_HERE"
}
}
}
}
Yempik Company Brain
{
"mcpServers": {
"yempik-company-brain": {
"command": "npx",
"args": [
"-y",
"yempik-company-brain"
]
}
}
}
Frequently asked questions
Deja Vu is categorized under Knowledge & Memory and uses a local stdio subprocess. Yempik Company Brain belongs to Knowledge & Memory and uses a remote HTTP/SSE transport. Pick Deja Vu for knowledge & memory work and Yempik Company Brain 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.
Deja Vu is listed as free. Auth: no auth required. Yempik Company Brain has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 vshulcz-deja-vu and yempik-company-brain as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Deja Vu has a quality signal of 65/100 (Great) with 8 views, 0 installs and 1,303 GitHub stars. Yempik Company Brain has 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.