Hermes — greatmemory docs

Hermes supports MCP stdio servers, so greatmemory can serve as its long-term memory backend.

Hermes' MCP configuration keys differ between versions and distributions. The snippets below use the widely-shared mcpServers JSON convention and a TOML equivalent — check your version's documentation for the exact key names and config file location before copying.

Setup

Install greatmemory first (local quickstart), then register the stdio server in your Hermes configuration.

JSON-style config:

{
  "mcpServers": {
    "greatmemory": {
      "command": "gmem",
      "args": ["mcp"],
      "env": {
        "GM_DATA_DIR": "/home/you/.greatmemory"
      }
    }
  }
}

TOML-style config:

[mcp_servers.greatmemory]
command = "gmem"
args = ["mcp"]
env = { GM_DATA_DIR = "/home/you/.greatmemory" }

Notes:

Prefer an absolute command path (e.g. /home/you/.cargo/bin/gmem) in case Hermes launches tools with a minimal PATH.
GM_DATA_DIR fixes where memories are stored; the default is ./.greatmemory relative to the process working directory.
stdio mode needs no running server — it opens the database directly. To share one live instance between several clients, run gmem serve and connect to http://127.0.0.1:7437/mcp over streamable HTTP instead (if your version supports HTTP MCP transports).

What you get

Five tools: remember, recall, get_context, get_profile, forget — parameters in the MCP reference.