WorkingMemory vs Cuba Memorys

In-depth architectural comparison of the WorkingMemory and Cuba Memorys 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?

W

Choose WorkingMemory when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore WorkingMemory Details

Choose Cuba Memorys when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Cuba Memorys Details

Feature & Specification Comparison

Specification	W WorkingMemory Knowledge & Memory	Cuba Memorys Knowledge & Memory
Summary	Persistent personal memory for AI assistants — save, search, and recall across every MCP client.	Persistent memory MCP server. 25 tools, BM25+MMR+OOD retrieval, CFR-21 audit, knowledge graph.
Category & Scope	Knowledge & Memory	Knowledge & Memory

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": {
    "workingmemory": {
      "command": "npx",
      "args": [
        "-y",
        "workingmemory"
      ]
    }
  }
}

{
  "mcpServers": {
    "cuba-memorys": {
      "command": "uvx",
      "args": [
        "memory-industry"
      ]
    }
  }
}

Related MCP Server Comparisons