Nautilus Compass vs SMRITI Memory

A side-by-side look at the Nautilus Compass and SMRITI Memory 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 declaredSMRITI Memory logoSMRITI MemoryKnowledge & Memory · Local subprocess (stdio)Neuro-inspired long-term memory for AI agents with semantic graph and consolidation.53GoodAuth: not declared

Verdict: choose Nautilus Compass for knowledge & memory work as a local process; choose SMRITI Memory 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?

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

SMRITI Memory logoChoose SMRITI Memory when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like smriti_encode, smriti_recall, smriti_get_context.
Explore SMRITI Memory

Feature & specification comparison

Rows where the two servers differ are marked.

SpecNautilus Compass logoNautilus CompassSMRITI Memory logoSMRITI Memory
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal47/100 · Fair53/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars1,2543
Directory activity 1 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
ToolsNot listed12

Tools & capabilities

Nautilus Compass tools

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

SMRITI Memory tools 12

  • smriti_encodeIngests a new memory. Accept `private=True` to exclude from team syncs.
  • smriti_recallRetrieves memories using semantic and graph-based retrieval.
  • smriti_get_contextHelper to inject the current active working memory slots into the context window.
  • smriti_how_well_do_i_knowPerforms a meta-memory confidence check on a given topic.
  • smriti_knowledge_gapsIdentifies topics the agent has identified it needs more information on.
  • smriti_pinMarks a memory as permanent (protects it from strength decay).
  • smriti_forgetSoft-deletes/archives a memory, leaving a cryptographic tombstone.
  • smriti_consolidateTriggers a background System 2 consolidation run.
  • smriti_statsReturns system-wide statistics (total memories, rooms, private counts).
  • smriti_create_private_roomSpawns a private room. All memories inside this room are visibility-isolated.
  • smriti_open_uiLaunches the interactive visual D3.js memory graph in your default browser.
  • smriti_sync_obsidianExports the Semantic Palace graph structures to markdown files in an Obsidian Vault.

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"
      ]
    }
  }
}

SMRITI Memory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "smriti-memory": {
      "command": "uvx",
      "args": [
        "smriti-memcore"
      ]
    }
  }
}

Frequently asked questions

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

Nautilus Compass has no declared pricing — check the project's own site. SMRITI Memory 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 nautilus-compass and smriti-memory 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,254 GitHub stars. SMRITI Memory has 53/100 (Good) with 0 views, 0 installs and 3 GitHub stars.