Memorix vs Nautilus Compass

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

Memorix logoMemorixKnowledge & Memory · Local subprocess (stdio)Local-first persistent project memory for AI coding agents across MCP clients and sessions.53GoodAuth: no auth requiredNautilus Compass logoNautilus CompassKnowledge & Memory · Local subprocess (stdio)Drift-aware cross-agent memory · MCP/A2A · LongMemEval-S 56.6% · 1/15 Zep cost47FairAuth: not declared

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

Which MCP server should you choose?

Memorix logoChoose Memorix when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: No auth required.
Explore Memorix

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMemorix logoMemorixNautilus Compass logoNautilus Compass
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal53/100 · Good47/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNo auth requiredNot declared
PricingFreeNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars8481,256
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Memorix tools

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

Nautilus Compass tools

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

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.

Memorix

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "memorix": {
      "command": "npx",
      "args": [
        "-y",
        "memorix"
      ]
    }
  }
}

Nautilus Compass

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

Frequently asked questions

Memorix is categorized under Knowledge & Memory and uses a local stdio subprocess. Nautilus Compass belongs to Knowledge & Memory and uses a local stdio subprocess. Pick Memorix for knowledge & memory work and Nautilus Compass 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.

Memorix is listed as free. Auth: no auth required. Nautilus Compass has no declared pricing — check the project's own site. 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 memorix and nautilus-compass as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Memorix has a quality signal of 53/100 (Good) with 2 views, 0 installs and 848 GitHub stars. Nautilus Compass has 47/100 (Fair) with 1 views, 0 installs and 1,256 GitHub stars.