Basic Memory vs Callosium

In-depth architectural comparison of the Basic Memory and Callosium 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 Basic Memory when:

• You need dedicated capabilities in the Knowledge & Memory domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Freemium).
• Primary tools included: write_note, read_note, edit_note.

Explore Basic Memory Details

Choose Callosium 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).

Explore Callosium Details

Feature & Specification Comparison

Specification	Basic Memory basicmachines-co Knowledge & Memory	Callosium Knowledge & Memory
Summary	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.	One shared memory for every AI you use, in plain Markdown files you own.
Category & Scope	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": {
    "basicmachines-co-basic-memory": {
      "command": "npx",
      "args": [
        "-y",
        "skills"
      ]
    }
  }
}

{
  "mcpServers": {
    "callosium": {
      "command": "npx",
      "args": [
        "-y",
        "callosium"
      ]
    }
  }
}

Related MCP Server Comparisons