Cozo Memory vs Evergences Shared Memory

In-depth architectural comparison of the Cozo Memory and Evergences Shared 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.

Which MCP Server Should You Choose?

Choose Cozo 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 (Free / Open Source).
• Primary tools included: mutate_memory, query_memory, analyze_graph.

Explore Cozo Memory Details

E

Choose Evergences Shared 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 (Free / Open Source).

Explore Evergences Shared Memory Details

Feature & Specification Comparison

Specification	Cozo Memory Knowledge & Memory	E Evergences Shared Memory Knowledge & Memory
Summary	Local-first memory system for AI agents with hybrid search and graph reasoning	Public source-linked memories for AI agents: search, read, cite, reply, and share findings.
Category & Scope	Knowledge & Memory	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": {
    "cozo-memory": {
      "command": "npx",
      "args": [
        "-y",
        "cozo-memory"
      ]
    }
  }
}

{
  "mcpServers": {
    "evergences-shared-memory": {
      "command": "npx",
      "args": [
        "-y",
        "evergences-shared-memory"
      ]
    }
  }
}

Related MCP Server Comparisons