Nautilus Compass vs Deja Vu

A side-by-side look at the Nautilus Compass and Deja Vu MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Nautilus Compass logoNautilus CompassKnowledge & Memory · Local subprocess (stdio)Drift-aware cross-agent memory · MCP/A2A · LongMemEval-S 56.6% · 1/15 Zep cost47FairAuth: not declaredDeja Vu logoDeja VuKnowledge & MemoryLocal 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.59GoodAuth: no auth required

Verdict: choose Nautilus Compass for knowledge & memory work as a local process; choose Deja Vu for knowledge & memory. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Nautilus Compass logoChoose Nautilus Compass when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
Explore Nautilus Compass

Deja Vu logoChoose Deja Vu when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • Its auth model fits you: No auth required.
  • You want tools like deja.
Explore Deja Vu

Feature & specification comparison

Rows where the two servers differ are marked.

SpecNautilus Compass logoNautilus CompassDeja Vu logoDeja Vu
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal47/100 · Fair59/100 · Good
Install commandConfirmedNot confirmed yet
TransportLocal subprocess (stdio)—
AuthNot declaredNo auth required
PricingNot declaredFree
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,2561,258
Directory activity 1 views 0 installs 0 upvotes 7 views 0 installs 0 upvotes
ToolsNot listed1

Tools & capabilities

Nautilus Compass tools

No tool names declared yet. Check the project README from the listing page.

Deja Vu tools 1

  • dejaDepends on the mode, below.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Nautilus Compass

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "nautilus-compass": {
      "command": "uvx",
      "args": [
        "nautilus-compass"
      ]
    }
  }
}

Deja Vu

No confirmed install command for Deja Vu yet — follow the setup steps linked from its listing page rather than a guessed package name.

Frequently asked questions

Nautilus Compass is categorized under Knowledge & Memory and uses a local stdio subprocess. Deja Vu belongs to Knowledge & Memory and uses an install path we have not confirmed yet. Pick Nautilus Compass for knowledge & memory work and Deja Vu for knowledge & memory.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Deja Vu has no confirmed install command yet — follow its own setup instructions.

Nautilus Compass has no declared pricing — check the project's own site. Deja Vu is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add nautilus-compass and vshulcz-deja-vu as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Nautilus Compass has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 1,256 GitHub stars. Deja Vu has 59/100 (Good) with 7 views, 0 installs and 1,258 GitHub stars.