Ainative Opencode Memory MCP vs Engram

In-depth architectural comparison of the Ainative Opencode Memory MCP and Engram 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 Ainative Opencode Memory MCP 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: opencode_store_memory, opencode_search_memory, opencode_recall_context.

Explore Ainative Opencode Memory MCP Details

E

Choose Engram 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: create_conversation, append_messages, search.

Explore Engram Details

Feature & Specification Comparison

Specification	Ainative Opencode Memory MCP Knowledge & Memory	E Engram Knowledge & Memory
Summary	Persistent cross-session memory for OpenCode and MCP coding agents, powered by ZeroDB.	Persistent memory for AI agents — verbatim conversations, searchable by meaning.
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": {
    "ainative-opencode-memory-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "ainative-opencode-memory-mcp"
      ]
    }
  }
}

{
  "mcpServers": {
    "engram-2": {
      "command": "npx",
      "args": [
        "-y",
        "@getengram/cli"
      ]
    }
  }
}

Related MCP Server Comparisons