MCP Persona Sessions vs Deja Vu
A side-by-side look at the MCP Persona Sessions 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 MCP Persona Sessions for knowledge & memory work; 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 MCP Persona Sessions when
- You need dedicated capabilities in the Knowledge & Memory domain.
- Its auth model fits you: No auth required.
- You want tools like
list_session_frameworks, list_session_personas, get_persona_details.
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 | 71/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 13 | 1,303 |
| Directory activity | 3 views 0 installs 0 upvotes | 8 views 0 installs 0 upvotes |
| Tools | 9 | 1 |
| Full listing | View MCP Persona Sessions | View Deja Vu |
Tools & capabilities
MCP Persona Sessions tools 9
list_session_frameworksBrowse available session types and templateslist_session_personasView all available personasget_persona_detailsGet full details of a specific personaassess_session_readinessCheck if ready to start a sessioninitialize_sessionBegin a structured sessionstart_timerStart session timer with optional durationcheck_timer_statusMonitor running timer progressstop_timerEnd timer and conclude sessionget_session_feedbackAnalyze session transcript for feedback
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.
MCP Persona Sessions
No confirmed install command for MCP Persona Sessions yet — follow the setup steps linked from its listing page rather than a guessed package name.
Deja Vu
{
"mcpServers": {
"vshulcz-deja-vu": {
"command": "npx",
"args": [
"-y",
"@vshulcz/deja-vu"
]
}
}
}
Frequently asked questions
MCP Persona Sessions is categorized under Knowledge & Memory and uses an install path we have not confirmed yet. Deja Vu belongs to Knowledge & Memory and uses a local stdio subprocess. Pick MCP Persona Sessions 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. MCP Persona Sessions has no confirmed install command yet — follow its own setup instructions.
MCP Persona Sessions is listed as free. Auth: no auth required. 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 mattjoyce-mcp-persona-sessions and vshulcz-deja-vu as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Persona Sessions has a quality signal of 40/100 (Fair) with 3 views, 0 installs and 13 GitHub stars. Deja Vu has 71/100 (Great) with 8 views, 0 installs and 1,303 GitHub stars.