Memstate MCP vs Deja Vu

In-depth architectural comparison of the Memstate MCP 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 Memstate MCP when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: MEMSTATE_API_KEY.
• Primary tools included: Hierarchical keypath-based memory, Automatic conflict detection, Full version history.

Explore Memstate MCP 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	Memstate MCP memstate-ai Knowledge & Memory	Deja Vu vshulcz Knowledge & Memory
Summary
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

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": {
    "memstate-ai-memstate-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@memstate/mcp"
      ],
      "env": {
        "MEMSTATE_API_KEY": "YOUR_MEMSTATE_API_KEY_HERE"
      }
    }
  }
}

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

Related MCP Server Comparisons