Being vs Central Intelligence — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Being vs Central Intelligence
In-depth architectural comparison of the Being and Central Intelligence 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.
At a Glance & Executive Verdict
Being
Knowledge & Memory · Remote HTTP/SSE
Quality: 45/100 (Fair) | Auth: API Key required
Central Intelligence
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Being if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Central Intelligence if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
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.
Personality Runtime for AI agents — persistent memory, identity (SOUL), and relationships that travel across Claude, OpenClaw, Mistral, and any MCP client.
Persistent memory for AI agents. Five tools (remember, recall, context, forget, share) with semantic search via vector embeddings and agent/user/org scoping. Works with Claude Code, Cursor, Windsurf, and any MCP client.
Category & Scope
Tools & Capabilities Breakdown
Being Tools (6)
Structured SOUL personality definitions
Scene-based episodic memory with decay and consolidation
Patrol background reflection and memory processing
Ed25519 identity keys and signature chains
MCP server and REST API access
Bring-your-own LLM API key support
Central Intelligence Tools (6)
Five MCP tools: remember, recall, context, forget, share
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).
Being is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Central Intelligence belongs to Knowledge & Memory using local stdio subprocess. Select Being when you need capabilities focused on knowledge & memory and Central Intelligence when you require tools for knowledge & memory.