meivo.Discuss your project

Agents

Hermes

stdio MCP configuration for Hermes.

Hermes supports MCP stdio servers, so Meivo 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 Meivo first (local quickstart), then register the stdio server in your Hermes configuration.

JSON-style config:

{
  "mcpServers": {
    "meivo": {
      "command": "gm-server",
      "args": ["mcp"],
      "env": {
        "GM_DATA_DIR": "/home/you/.greatmemory"
      }
    }
  }
}

TOML-style config:

[mcp_servers.meivo]
command = "gm-server"
args = ["mcp"]
env = { GM_DATA_DIR = "/home/you/.greatmemory" }

Notes:

  • Prefer an absolute command path (e.g. /home/you/.cargo/bin/gm-server) 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 trusted clients, run gm-server serve and connect to http://127.0.0.1:7437/mcp over streamable HTTP instead (if your version supports HTTP MCP transports).
  • space is a retrieval namespace, not an authorization boundary. A direct MCP client can select any space in the store. Use separate data directories for untrusted users or route shared enterprise access through the governance gateway.

What you get

Thirteen tools cover remember, recall, cited context, profiles, temporal history, episodes, linked cards, and forget. See the MCP reference for parameters.