Claude Memory Manager vs Deja Vu

In-depth architectural comparison of the Claude Memory Manager and Deja Vu MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Claude Memory Manager when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: memory_search, memory_recall, memory_save.

Explore Claude Memory Manager Details

Choose Deja Vu when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: deja.

Explore Deja Vu Details

Feature & Specification Comparison

Specification	Claude Memory Manager Knowledge & Memory	Deja Vu vshulcz Knowledge & Memory
Summary	Cross-session memory for Claude Code — context capture, semantic search, recall	Local memory layer over the session histories coding agents already write (Claude Code, Codex CLI, opencode): lexical search, recall tools, session-start auto-recall, secret redaction at index time, cross-machine sync over SSH.
Category & Scope	Knowledge & Memory

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "claude-memory-manager": {
      "command": "uvx",
      "args": [
        "claude-memory-manager"
      ]
    }
  }
}

{
  "mcpServers": {
    "vshulcz-deja-vu": {
      "command": "npx",
      "args": [
        "-y",
        "@vshulcz/deja-vu"
      ]
    }
  }
}

Related MCP Server Comparisons