Clude vs N3MemoryCore Lite (Working Memory)

In-depth architectural comparison of the Clude and N3MemoryCore Lite (Working Memory) MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

C

Choose Clude when:

• You need dedicated capabilities in the Databases domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: recall_memories, store_memory, batch_store_memories.

Explore Clude Details

Choose N3MemoryCore Lite (Working Memory) when:

• You need dedicated capabilities in the Databases domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: search_memory, save_memory, list_memories.

Explore N3MemoryCore Lite (Working Memory) Details

Feature & Specification Comparison

Specification	C Clude Databases	N3MemoryCore Lite (Working Memory) Databases
Summary	Portable agent memory anchored on Solana. Local SQLite + vector recall, open export.	Ephemeral 7-day hybrid vector+BM25 working memory, multilingual, backed by Redis Stack.
Category & Scope	Databases	Databases
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "clude": {
      "command": "npx",
      "args": [
        "-y",
        "@clude/sdk"
      ]
    }
  }
}

{
  "mcpServers": {
    "n3memorycore-lite-working-memory": {
      "command": "uvx",
      "args": [
        "--from"
      ]
    }
  }
}

Related MCP Server Comparisons