Cortex vs Deja Vu
A side-by-side look at the Cortex 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 Cortex 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?
Choose Cortex when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
CORTEX_ACCESS_TOKEN, CORTEX_MCP_URL.
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 | 40/100 · Fair | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | CORTEX_ACCESS_TOKENCORTEX_MCP_URL | None listed |
Tools & capabilities
Cortex 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.
Cortex
{
"mcpServers": {
"cortex-5": {
"url": "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"
}
}
}
Deja Vu
{
"mcpServers": {
"vshulcz-deja-vu": {
"command": "npx",
"args": [
"-y",
"@vshulcz/deja-vu"
]
}
}
}
Frequently asked questions
Cortex 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 Cortex 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.
Cortex 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 cortex-5 and vshulcz-deja-vu as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cortex has a quality signal of 40/100 (Fair) with 1 views, 0 installs and 1 GitHub stars. Deja Vu has 69/100 (Great) with 2 views, 0 installs and 1,146 GitHub stars.