What this connection does
OmO Native can retrieve existing observations from a running local Claude-Mem worker. The configuration below exposes the read-onlysearch, timeline, and get_observations tools. The scope is on-demand recall.
Use the standalone omo command. The OmO Native migration guide explains how to distinguish it from the OpenCode edition. For Claude-Mem’s OpenCode plugin, see the platform integration guide.
Setup
You need an existing Claude-Mem installation with a local worker, Node.js 24 or newer, and OmO Native with a configured model for interactive prompts. The local MCP connection uses the worker’s existing settings. OmO may pass returned memory to the model provider selected for the session.- Start your Claude-Mem worker normally. Locate the absolute path to
plugin/scripts/mcp-server.cjsin that installation. - Back up OmO’s
~/.omo/agent/mcp.json, if it exists. If you setOMO_CODING_AGENT_DIR, use themcp.jsonin that directory. - Add the
claude-mementry insidemcpServers. Keep existing server entries and settings. If aclaude-mementry already exists, review it before replacing it. - Replace the example path, then start a new OmO session.
CLAUDE_MEM_DATA_DIR or CLAUDE_MEM_WORKER_PORT, pass the same values in the entry’s env. Leave local API tokens in the worker’s settings file. See worker configuration for details.
Verify recall
- Choose a non-sensitive observation already saved in a test project. Note the project name and observation ID.
- In OmO, run
/mcpand check thatclaude-memconnects. Ask OmO to use the Claude-Memget_observationstool for that ID and project. - Compare the tool result with the known observation. For discovery when you only know a topic, use
searchwith the project name, thentimelineandget_observationsfor selected matches.
Troubleshoot and disconnect
- Server or tools missing. Verify the MCP config directory, absolute script path, and
nodeon the same PATH OmO uses. Check/mcpafter restarting the session. - Worker unavailable. Verify the configured worker is running and the MCP entry uses its data directory and port. The entry leaves worker lifecycle management to your existing Claude-Mem setup.
- No matching observation. Check the project name and numeric observation ID. Use a test project with a known saved record to distinguish an empty result from a connection problem.
mcpServers.claude-mem from OmO’s config and restart OmO. The worker and its saved observations remain available to your other clients.
References · OmO Native documentation · OmO Native configuration migration · Claude-Mem memory search
