What is the key difference between Mnemos and Deja Vu?

Mnemos belongs to the Knowledge & Memory category with local stdio execution, while Deja Vu belongs to the Knowledge & Memory category with local stdio execution.

How do I install Mnemos or Deja Vu in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Mnemos and Deja Vu free or paid?

Mnemos operates under a Free / Open Source model (No auth required). Deja Vu operates under a Free / Open Source model (No auth required).

Which MCP server has more tools and community activity?

Mnemos lists 9 tools with 2 views and 22 GitHub stars. Deja Vu lists 1 tools with 2 views and 824 GitHub stars.

Can I use both Mnemos and Deja Vu together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Mnemos vs Deja Vu

In-depth architectural comparison of the Mnemos 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.

At a Glance & Executive Verdict

Mnemos

Knowledge & Memory · Local stdio

Quality: 59/100 (Good) | Auth: No auth required

Deja Vu

Knowledge & Memory · Local stdio

Quality: 68/100 (Great) | Auth: No auth required

Verdict Summary: Choose Mnemos if you need specialized Knowledge & Memory tools running via a local process. Choose Deja Vu if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Mnemos 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: mnemos_store, mnemos_search, mnemos_context.

Explore Mnemos 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	Mnemos s60yucca Knowledge & Memory	Deja Vu vshulcz Knowledge & Memory
Summary	Persistent memory engine for AI coding agents. Stores architecture decisions, bug root causes, and project conventions across sessions. Single Go binary with embedded SQLite, FTS5 search, context assembly within token budgets, and autopilot setup for Claude Code, Kiro, and Cursor.	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

Mnemos Tools (9)

mnemos_store

Store a memory (full auto-pipeline runs transparently)

mnemos_search

Hybrid FTS + semantic + file-overlap search

mnemos_context

Assemble budget-aware, MMR-diversified context

mnemos_get

Fetch by ID

mnemos_update

Update content, summary, or tags

mnemos_delete

Soft-delete (recoverable via maintain)

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).

Mnemos Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "s60yucca-mnemos": {
      "command": "npx",
      "args": [
        "-y",
        "@s60yucca/mnemos"
      ]
    }
  }
}

Deja Vu Configuration

mcpServers (Claude Desktop / Cursor)

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

Frequently Asked Questions

Mnemos is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Deja Vu belongs to Knowledge & Memory using local stdio subprocess. Select Mnemos when you need capabilities focused on knowledge & memory and Deja Vu when you require tools for knowledge & memory.

More alternatives to Mnemos More alternatives to Deja Vu Knowledge & Memory category hub