Awareness Local vs Central Intelligence

In-depth architectural comparison of the Awareness Local 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.

Which MCP Server Should You Choose?

A

Choose Awareness Local when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: awareness_init, awareness_recall, awareness_record.

Explore Awareness Local Details

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 memory tools, Semantic search with scoped memories, Agent, user, and organization visibility.

Feature & Specification Comparison

Specification	A Awareness Local Knowledge & Memory	Central Intelligence AlekseiMarchenko Knowledge & Memory
Summary
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": {
    "awareness-local": {
      "command": "npx",
      "args": [
        "-y",
        "@awareness.market/setup"
      ]
    }
  }
}

{
  "mcpServers": {
    "alekseimarchenko-central-intelligence": {
      "command": "npx",
      "args": [
        "-y",
        "central-intelligence-local"
      ],
      "env": {
        "CI_API_KEY": "YOUR_CI_API_KEY_HERE"
      }
    }
  }
}

Related MCP Server Comparisons