Dexio vs Deja Vu

In-depth architectural comparison of the Dexio 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?

D

Choose Dexio when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: other (Freemium).
• Primary tools included: MCP access to wiki pages, Page reading and writing, Wiki link graph.

Explore Dexio 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	D Dexio VerifiedKnowledge & Memory	Deja Vu vshulcz Knowledge & Memory
Summary	One wiki for all your agents: pages read and written over MCP, a link graph, and broken-link checks. Remote MCP server at https://app.dexio.wiki/mcp (Streamable HTTP; OAuth or a bearer API key).	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

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": {
    "dexio": {
      "url": "https://app.dexio.wiki/mcp"
    }
  }
}

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

Related MCP Server Comparisons