RCLL vs Worldku Memory

In-depth architectural comparison of the RCLL 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?

R

Choose RCLL 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_retain, memory_recall, memory_reflect.

Explore RCLL 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	R RCLL Knowledge & Memory	Worldku Memory Knowledge & Memory
Summary	Self-hosted shared memory for a team of AI agents. Rooms, L0-L3 depth, no LLM on the read path.	Save AI conversations into your Worldku memory and recall them from any MCP client.
Category & Scope	Knowledge & Memory	Knowledge & Memory
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": {
    "rcll": {
      "url": "https://godcrm.ai/git/holetron-lab/fleet-memory"
    }
  }
}

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

Related MCP Server Comparisons