Fidelis Memory vs Nautilus Compass

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

Fidelis Memory logoFidelis MemoryKnowledge & Memory · Local subprocess (stdio)Recall locally stored agent memories through an MCP-compatible host.43FairAuth: not declaredNautilus 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 Fidelis Memory 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?

Fidelis Memory logoChoose Fidelis Memory when

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

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.

SpecFidelis Memory logoFidelis MemoryNautilus Compass logoNautilus Compass
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal43/100 · Fair47/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars241,254
Directory activity 1 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Fidelis Memory 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.

Fidelis Memory

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "fidelis-memory": {
      "command": "uvx",
      "args": [
        "--from",
        "fidelis-memory",
        "fidelis-mcp"
      ]
    }
  }
}

Nautilus Compass

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

Frequently asked questions

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

Fidelis Memory has no declared pricing — check the project's own site. 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 fidelis-memory and nautilus-compass as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Fidelis Memory has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 24 GitHub stars. Nautilus Compass has 47/100 (Fair) with 1 views, 0 installs and 1,254 GitHub stars.