Claude Memory Manager vs Worldku Memory

In-depth architectural comparison of the Claude Memory Manager and Worldku 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?

Choose Claude Memory Manager 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).
• Primary tools included: memory_search, memory_recall, memory_save.

Explore Claude Memory Manager Details

Choose Worldku Memory when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: memory_overview, memory_search, memory_recall.

Explore Worldku Memory Details

Feature & Specification Comparison

Specification	Claude Memory Manager Knowledge & Memory	Worldku Memory Knowledge & Memory
Summary	Cross-session memory for Claude Code — context capture, semantic search, recall	Save AI conversations into your Worldku memory and recall them from any MCP client.
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": {
    "claude-memory-manager": {
      "command": "uvx",
      "args": [
        "claude-memory-manager"
      ]
    }
  }
}

{
  "mcpServers": {
    "worldku-memory": {
      "url": "https://www.worldku.com"
    }
  }
}

Related MCP Server Comparisons