Being vs Recallnest

In-depth architectural comparison of the Being and Recallnest 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 Being when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY, ENCRYPTION_KEY.
• Primary tools included: Structured SOUL personality definitions, Scene-based episodic memory with decay and consolidation, Patrol background reflection and memory processing.

Explore Being Details

Choose Recallnest when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Free / Open Source).
• You have access to required keys: JINA_API_KEY.

Feature & Specification Comparison

Specification	Being wnbhr Knowledge & Memory	Recallnest AliceLJY Knowledge & Memory
Summary	Personality Runtime for AI agents — persistent memory, identity (SOUL), and relationships that travel across Claude, OpenClaw, Mistral, and any MCP client.	Persistent memory MCP server for AI coding agents (Claude Code, Codex, Gemini CLI). Hybrid retrieval (vector + BM25), cross-encoder reranking, knowledge graph with PPR traversal, session checkpoint/resume, and multi-scope isolation. Local-first with LanceDB + SQLite, zero external dependencies.
Category & Scope

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": {
    "wnbhr-being": {
      "url": "https://being.ruddia.com/mcp/"
    }
  }
}

{
  "mcpServers": {
    "aliceljy-recallnest": {
      "command": "npx",
      "args": [
        "-y",
        "recallnest"
      ],
      "env": {
        "JINA_API_KEY": "YOUR_JINA_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons