Quickstart
Connect any AI agent to MemClaw in five minutes — pick managed, self-hosted, or REST.
You have three integration paths. Pick the one that matches your stack:
| Path | When to use | Setup time |
|---|---|---|
| OpenClaw | You run a fleet of agents and want them all to share memory | ~3 min |
| MCP | A single client (Claude Desktop, Claude Code, Cursor, Windsurf) | ~1 min |
| REST | Custom code in any language | ~30 sec |
Create an API key
For the managed deployment, sign in at /signin and generate a tenant-scoped key from Settings → API Keys. Keys start with mc_.
For self-hosted OSS, pick one auth mode in your .env:
# Single-tenant, no key needed
IS_STANDALONE=true
# Or: multi-tenant, full access
ADMIN_API_KEY=admin_xxx
# Or: shared gate (key + X-Tenant-ID header)
MEMCLAW_API_KEY=mc_xxxPick your path
Run on the gateway host:
curl -s -H "X-API-Key: $MEMCLAW_API_KEY" \
"https://memclaw.net/api/v1/install-plugin?fleet_id=YOUR_FLEET_ID" | bashThe installer downloads the plugin, builds it, edits ~/.openclaw/openclaw.json to claim the memory slot, and writes the env file. Restart the gateway:
openclaw gateway restartPaste this into your MCP client config (claude_desktop_config.json, ~/.cursor/config.json, etc.):
{
"mcpServers": {
"memclaw": {
"url": "https://memclaw.net/mcp",
"headers": { "X-API-Key": "mc_xxx" }
}
}
}Restart the client. The memclaw_* tools become available.
For anything beyond a single user — a team or fleet of agents — bind each agent to its own agent-scoped credential instead of sharing the tenant-scoped key. See Per-agent keys for the atomic-provisioning flow that mints the credential, the Agent row, and trust level in one call. Both kinds use the mc_ prefix on the wire — scope is bound at mint time on the credential row.
No install. Hit the API directly from any language:
curl -X POST "https://memclaw.net/api/v1/memories" \
-H "X-API-Key: mc_xxx" \
-H "Content-Type: application/json" \
-d '{ "tenant_id": "YOUR_TENANT_ID", "content": "User prefers dark mode." }'Verify
curl "https://memclaw.net/api/v1/health" -H "X-API-Key: mc_xxx"
# {"status": "ok", "storage": "connected", "redis": "connected", "event_bus": "ok"}A 503 means a required dependency is unhealthy (storage / redis / event_bus). For OpenClaw installs, your node should appear in Fleet Management within 60 seconds of the first heartbeat (HEARTBEAT_INTERVAL_SECONDS = 60 per core-api/src/core_api/constants.py).
Write your first memory
For OpenClaw and MCP, just talk to your agent:
Remember that I prefer concise answers and dark mode.
Then ask later:
What do you know about my UI preferences?
The agent calls memclaw_write and memclaw_recall automatically. The exact write response shape is defined by the MemoryOut schema in core-api/src/core_api/schemas.py (id, tenant_id, fleet_id, agent_id, memory_type, title, content, weight, entity_links, status, …).