Central Intelligence vs Engram Rs

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

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
• You have access to required keys: ENGRAM_EMBEDDING_PROVIDER, ENGRAM_EMBEDDING_API_KEY.

Feature & Specification Comparison

Specification	Central Intelligence AlekseiMarchenko Knowledge & Memory	Engram Rs kael-bit Knowledge & Memory
Summary	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.	Hierarchical memory engine for AI agents with automatic decay, promotion, semantic dedup, and self-organizing topic tree. Single Rust binary, 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": {
    "alekseimarchenko-central-intelligence": {
      "command": "npx",
      "args": [
        "-y",
        "central-intelligence-local"
      ],
      "env": {
        "CI_API_KEY": "YOUR_CI_API_KEY_HERE"
      }
    }
  }
}

{
  "mcpServers": {
    "kael-bit-engram-rs": {
      "command": "npx",
      "args": [
        "-y",
        "engram-rs-mcp"
      ],
      "env": {
        "ENGRAM_EMBEDDING_PROVIDER": "YOUR_ENGRAM_EMBEDDING_PROVIDER_HERE",
        "ENGRAM_EMBEDDING_API_KEY": "YOUR_ENGRAM_EMBEDDING_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons