Engram

Engram runs locally from a Node.js package published to the npm registry: engramx version 4.5.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y engramx@4.5.0; the entry names node as the runtime. It reads these environment variables: ENGRAM_API_TOKEN (secret), ENGRAM_MISTAKE_GUARD, ENGRAM_ANTHROPIC_MEMORY_PATH, ENGRAM_MCP_CONFIG_PATH and ENGRAM_NO_UPDATE_CHECK; set them in the client's configuration for this server. Required arguments: binary.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "engram": {
      "command": "npx",
      "args": [
        "-y",
        "engramx@4.5.0"
      ],
      "env": {
        "ENGRAM_API_TOKEN": "<secret>",
        "ENGRAM_MISTAKE_GUARD": "<value>",
        "ENGRAM_ANTHROPIC_MEMORY_PATH": "<value>",
        "ENGRAM_MCP_CONFIG_PATH": "<value>",
        "ENGRAM_NO_UPDATE_CHECK": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect