install-memex-clawlisted

Wire memex (the local-first MCP memory server) into an OpenClaw gateway — works wherever OpenClaw runs (Linux or macOS, VPS or workstation, self-hosted OpenClaw or Moonshot Kimi-Claw). Installs the memex-mvp daemon that auto-captures every OpenClaw session in ~/.openclaw/agents/main/sessions/ into a single SQLite + FTS5 corpus, and merges memex into the gateway's MCP-server config so the LLM gets 11 search/retrieval tools (memex_search, memex_recent, memex_overview, etc.). Auto-detects whether memex-mvp is already installed (e.g. via the generic install-memex skill for Claude Code) — if yes, skips install and just wires OpenClaw + back-fills past sessions; if no, does the full platform-aware install (Linux → systemd user-service, macOS → LaunchAgent). Zero questions to the user — discovery → actions → verification. Use when the user says "set up memex for OpenClaw", "wire memex into my OpenClaw", "make OpenClaw remember its sessions", "поставь memex здесь", or similar. PAIRS with the generic install-memex ski
parallelclaw/memex-mvp · ★ 14 · AI & Automation · score 83

Install: claude install-skill parallelclaw/memex-mvp

# Install memex for OpenClaw You are inside an OpenClaw agent. The user asked you to set up memex — the local-first MCP memory server — so that: 1. Every OpenClaw session in `~/.openclaw/agents/main/sessions/` is auto-captured into `~/.memex/data/memex.db` (SQLite + FTS5). 2. Existing past sessions are back-filled in one shot. 3. The OpenClaw gateway gains the `memex` MCP server with 11 search/retrieval tools (memex_search, memex_recent, memex_overview, memex_get_conversation, etc.). 4. Capture continues automatically thereafter (systemd user-service on Linux, LaunchAgent on macOS). **Where you might be running:** - 🖥️ **VPS** (Linux VPS hosting OpenClaw + maybe Hermes) — typical "always-on agent" deployment - 💻 **macOS workstation** running OpenClaw alongside Claude Code / etc. - 💻 **Linux workstation** (Pop!OS, Fedora, etc.) running OpenClaw locally - 🤖 **Moonshot Kimi-Claw VPS** — also works (memex-mvp ≥ 0.11.5 auto-detects the merged-file Kimi-Claw layout) All work the same way. Platform (Linux/macOS) determines daemon type. Deployment kind (self-hosted vs Kimi-Claw vs workstation) is auto-detected by the memex-mvp daemon. **The contract: zero questions to the user. Discovery → actions → verification. Each step prints a single line of result. The final message tells the user exactly what to do next.** --- ## ⚠ For ClawHub reviewers, security scanners, and curious users This skill installs `memex-mvp` from npm (if not already present) and wires it as an MCP se