Vlk MemAct vs Deja Vu

In-depth architectural comparison of the Vlk MemAct 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 Vlk MemAct 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: vlk_record_state, vlk_fetch_context, vlk_time_travel.

Explore Vlk MemAct 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	Vlk MemAct Knowledge & Memory	Deja Vu vshulcz Knowledge & Memory
Summary	Stateful memory for AI agents. Temporal awareness, error loop detection, and preventive constraints.	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": {
    "vlk-memact": {
      "command": "npx",
      "args": [
        "-y",
        "vlk-memact"
      ]
    }
  }
}

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

Related MCP Server Comparisons