OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Agent Memory & RAG

OpenClaw Mem0 Memory Plugin

OpenClaw Mem0 Memory Plugin is a TypeScript extension that connects OpenClaw to a self-hosted Mem0 REST API for persistent semantic agent memory. It offers tools and CLI commands to recall, store, list and forget memories, and can automatically retrieve relevant memories before agent runs and capture conversation highlights afterward.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

OpenClaw Mem0 Memory Plugin — OpenViST project profile in Agent Memory & RAG.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when an OpenClaw agent needs Mem0-backed semantic memory and you can provide a compatible, running Mem0 REST API.

Who it is for

  • OpenClaw operators who want agents to retain and retrieve information across runs.
  • Developers deploying a self-hosted Mem0 service and connecting it to OpenClaw.

Documented uses

  • Search stored memories for facts relevant to an agent’s current prompt.
  • Store a fact for later recall or delete a memory by ID.
  • Automatically add relevant memories to agent context and send conversation content for memory extraction.
  • Search, list and forget memories using OpenClaw CLI commands.
Before you choose

Requirements & limits

The repository identifies the plugin as open source under the MIT license and describes it as self-hosted. It requires a running Mem0 REST API.

  • The plugin replaces OpenClaw’s default LanceDB memory backend through the memory slot; the README says the slot can be switched back.
  • The Mem0 server performs LLM-based fact extraction and embedding-based vector search; these are not performed by the plugin itself.
  • Automatic recall and capture are configurable, as are the recall limit and relevance threshold.
  • The plugin expects a compatible REST API for health checks, searching, storing, listing and deleting memories.
  • The README says the plugin uses Node.js built-in fetch and has no native dependencies or SDK requirement.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Install and configure the plugin

Add the extension to OpenClaw and configure it to use an existing Mem0 REST API.

Before you start

  • An OpenClaw installation with a user extensions directory and configuration file.
  • A running Mem0 REST API, or another HTTP server implementing the expected health, memory search, create, list and delete endpoints.
  • The plugin repository copied or otherwise available locally.

Steps

  1. Copy the plugin into ~/.openclaw/extensions/memory-mem0 and run npm install in that directory.

  2. Set the OpenClaw memory slot to memory-mem0 and enable the plugin entry; configure baseUrl and userId, and set autoRecall, autoCapture and recall options as needed.

  3. Restart the OpenClaw gateway using the documented user systemd command.

  4. Check the gateway logs for the plugin registration message.

Expected outcome

OpenClaw is configured to use the Mem0-backed memory plugin, with automatic recall and capture enabled if configured.

Guide limitations

  • A running compatible Mem0 REST API is required; this procedure does not set up that server.
  • The documented restart command uses systemd user services.
  • The README recommends 127.0.0.1 rather than localhost on Node.js 22+ when the Mem0 service binds only to IPv4.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
16 October 2026
Original website title
serenichron/openclaw-memory-mem0 · Official homepage title · retained in its source language
How we review sourcesSuggest a correction

Related options

OpenClaw’s default LanceDB memory backend — The plugin replaces this backend through OpenClaw’s memory slot; the README says the slot can be reverted and the memory tool names are shared.