Engram vs Repo Memory

In-depth architectural comparison of the Engram and Repo 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 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).

Explore Engram Details

Choose Repo 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 Repo Memory Details

Feature & Specification Comparison

Specification	Engram Knowledge & Memory	Repo Memory Knowledge & Memory
Summary	MCP adapter for Engram - organizational memory for AI agents	Shared, git-tracked working memory for AI agents on the same codebase.
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": {
    "engram-3": {
      "command": "npx",
      "args": [
        "-y",
        "@spectra-g/engram-adapter"
      ]
    }
  }
}

{
  "mcpServers": {
    "repo-memory": {
      "command": "uvx",
      "args": [
        "repo-memory-mcp"
      ]
    }
  }
}

Related MCP Server Comparisons