Agent Magnet vs Nautilus Compass

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

Agent Magnet logoAgent MagnetKnowledge & Memory · Local subprocess (stdio)Behavioral memory layer for AI tools. Learns preferences and context across Claude, Cursor, Codex.41FairAuth: 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 Agent Magnet 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?

Agent Magnet logoChoose Agent Magnet when

  • You need dedicated capabilities in the Knowledge & Memory domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: MAGNET_USER_ID.
Explore Agent Magnet

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.

SpecAgent Magnet logoAgent MagnetNautilus Compass logoNautilus Compass
CategoryKnowledge & MemoryKnowledge & Memory
Quality signal41/100 · Fair47/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsMAGNET_USER_IDNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars141,254
Directory activity 0 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

Agent Magnet 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.

Agent Magnet

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "agent-magnet": {
      "command": "uvx",
      "args": [
        "agent-magnet"
      ],
      "env": {
        "MAGNET_USER_ID": "YOUR_MAGNET_USER_ID_HERE"
      }
    }
  }
}

Nautilus Compass

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

Frequently asked questions

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

Agent Magnet 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 agent-magnet and nautilus-compass as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Agent Magnet has a quality signal of 41/100 (Fair) with 0 views, 0 installs and 14 GitHub stars. Nautilus Compass has 47/100 (Fair) with 1 views, 0 installs and 1,254 GitHub stars.