In-depth architectural comparison of the Central Intelligence and Basic Memory 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
Central Intelligence
Knowledge & Memory · Local stdio
Quality: 49/100 (Fair) | Auth: API Key required
Basic Memory
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Central Intelligence if you need specialized Knowledge & Memory tools running via a local process. Choose Basic Memory 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 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.
Central Intelligence is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Basic Memory belongs to Knowledge & Memory using local stdio subprocess. Select Central Intelligence when you need capabilities focused on knowledge & memory and Basic Memory when you require tools for knowledge & memory.
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.
Persistent, local-first AI memory: a semantic knowledge graph of plain Markdown files that humans and LLMs both read and write. Works with any MCP client, with optional cloud sync and team workspaces.