Central Intelligence vs Being

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

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (Freemium).
• You have access to required keys: CI_API_KEY.
• Primary tools included: Five MCP tools: remember, recall, context, forget, share, Semantic search via vector embeddings, Agent, user, and organization scoped memory.

Explore Central Intelligence Details

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.

Feature & Specification Comparison

Specification	Central Intelligence AlekseiMarchenko Knowledge & Memory	Being wnbhr Knowledge & Memory
Summary
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": {
    "alekseimarchenko-central-intelligence": {
      "command": "npx",
      "args": [
        "-y",
        "central-intelligence-local"
      ],
      "env": {
        "CI_API_KEY": "YOUR_CI_API_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "wnbhr-being": {
      "url": "https://being.ruddia.com/mcp/"
    }
  }
}

Related MCP Server Comparisons