Five steps to give your LLM agents persistent, governed memory with MemClaw.
MemClaw has two deployment modes. Pick the one that matches your setup:
Sign in at /signin, then create a tenant-scoped key from Manage → API Keys. Keys start with mc_.
Pick one auth mode in your .env:
IS_STANDALONE=true — single tenant (tenant_id="default"), no key neededADMIN_API_KEY=… — multi-tenant, full access via that single keyMEMCLAW_API_KEY=… with per-request X-Tenant-ID header — shared-gate for multi-tenant self-hostedOpenClaw Gateway. Installs the MemClaw plugin on a gateway host. Every agent routed through the gateway gets persistent memory, the knowledge graph, auto-write on turn boundaries, and the full 12-tool surface. Pick this if you’re running a fleet.
SSH into the OpenClaw gateway host and run this one-liner. It downloads the plugin source, builds, configures openclaw.json, and writes the plugin .env:
curl -s -H "X-API-Key: YOUR_API_KEY" \ "https://memclaw.net/api/v1/install-plugin?fleet_id=YOUR_FLEET_ID" | bash
Requires curl, node (v18+), and npm on the gateway. The node appears in the Fleet page within 60 seconds.
# What the installer does (manual path): # 1. Downloads all plugin source files to ~/.openclaw/plugins/memclaw/ # 2. Runs npm install && npm run build # 3. Edits ~/.openclaw/openclaw.json to claim the 'memory' slot, # disable memory-core, and allowlist the 10 memclaw_ tools. # 4. Writes .env with MEMCLAW_API_KEY, MEMCLAW_FLEET_ID, MEMCLAW_API_URL. # # Then restart the gateway: openclaw gateway restart # or: systemctl --user restart openclaw-gateway
Hit the health endpoint to confirm the API is reachable and your key is accepted:
curl "https://memclaw.net/api/v1/health" \
-H "X-API-Key: YOUR_API_KEY"
# Expected response:
# {"status": "ok", "database": "connected", "version": "..."}For OpenClaw gateway installs: also check the Fleet page — your node should appear within 60 seconds of the first heartbeat.
Ask any agent on the gateway to remember something. The plugin auto-calls memclaw_write on meaningful turn boundaries, but you can also trigger it explicitly:
"Remember that our auth service uses JWT with 15-minute expiry."
Later, recall it via a prompt like “What do you know about our auth service?” — the plugin calls memclaw_recall automatically.