#Mem0 install

1 messages · Page 1 of 1 (latest)

scarlet matrix
#

Tell me about how mem0 works with openclaw, and what the install process is.

severe roostBOT
#

OpenClaw doesn’t currently have a built-in “mem0 backend” where memory_search automatically talks to mem0.

1) How OpenClaw memory works (built-in)

OpenClaw’s memory is local Markdown in your agent workspace:

  • memory/YYYY-MM-DD.md = daily log
  • MEMORY.md = curated long-term memory (only loaded in the private/main session)

On top of that, OpenClaw can build a semantic (vector) index over those files so memory_search can recall relevant snippets even if the wording differs.

Docs:

2) So where does mem0 fit?

Mem0/OpenMemory is a separate memory service (with an MCP server). With OpenClaw today, you typically use it as an external tool, not as the internal memory engine.

#

Practically, that means:

  • OpenClaw’s memory_search / memory_get keep working against your local Markdown files.
  • If you want mem0, you expose it to the agent as callable tools (usually via MCP, commonly through the mcporter skill), and the agent calls mem0 explicitly.

3) Mem0/OpenMemory install (the “server”)

From mem0’s OpenMemory README (external project): it’s Docker-based and expects an OPENAI_API_KEY. It runs:

  • API/MCP server at http://localhost:8765 (docs at /docs)
  • UI at http://localhost:3000

OpenMemory README (install steps):
https://github.com/mem0ai/mem0/tree/main/openmemory

4) Hooking OpenMemory into OpenClaw (high level)

The OpenClaw-native way is:

  1. Enable/install the mcporter skill (it’s OpenClaw’s “MCP client/manager” skill)
  2. Point mcporter at the OpenMemory MCP endpoint (OpenMemory uses URLs shaped like http://localhost:8765/mcp/<client>/sse/<user-id>)
  3. Verify available tools via mcporter, then call them from the agent when you want “mem0 memory”
#

mcporter skill reference (bundled with OpenClaw): https://github.com/openclaw/openclaw/tree/main/skills/mcporter

If you tell me your target setup (OpenMemory on same machine as the Gateway vs remote/VPS, and whether you’re aiming for “explicit tool calls” vs “replace OpenClaw memory”), I can suggest the cleanest wiring.