Agents
Codex CLI
Register gm-server mcp in ~/.codex/config.toml.
Codex CLI configures MCP servers in ~/.codex/config.toml.
Setup
Install Meivo first (local quickstart), then add:
# ~/.codex/config.toml
[mcp_servers.meivo]
command = "gm-server"
args = ["mcp"]
To share one memory store across all your projects, pin the data dir to an absolute path (otherwise it resolves to ./.greatmemory relative to wherever Codex launches the process):
[mcp_servers.meivo]
command = "gm-server"
args = ["mcp"]
[mcp_servers.meivo.env]
GM_DATA_DIR = "/Users/you/.greatmemory"
Restart Codex; thirteen memory tools become available, covering remember, recall, cited context, profiles, temporal history, episodes, linked cards, and forget. See the MCP reference for parameters.
No separate server process is needed - gm-server mcp opens the database
directly.
Usage
Ask Codex to "remember that ..." to store durable notes, and "what do you know about ..." to retrieve them in later sessions. Use a distinct space per project if you point several projects at one shared data dir.
space is a retrieval namespace, not an authorization boundary. A direct MCP
client can select any space in that store, so use separate data directories for
untrusted clients or route shared enterprise access through the governance
gateway.
Troubleshooting
- If the server fails to start, use an absolute path for
command(e.g."/Users/you/.cargo/bin/gm-server") - GUI-launched processes often have a minimalPATH. - The first tool call downloads the embedding model (one-time, a few tens of MB); subsequent calls are fast and offline.