Memory

ViBo MCP

Try it

Local-first memory for AI agents over MCP: persistent memory (L1/L2/L3), web-search savings, thread memory. Works with Claude Desktop, Cursor, OpenClaw, Windsurf, Codex. Requires a valid ViBo license. Everything is stored locally on the user's machine; use ONLY with the user's explicit consent.

What it does

Local-first memory for AI agents over MCP: persistent memory (L1/L2/L3), web-search savings, thread memory. Works with Claude Desktop, Cursor, OpenClaw, Windsurf, Codex. Requires a valid ViBo license. Everything is stored locally on the user's machine; use ONLY with the user's explicit consent.

The skill document

ViBo MCP — local-first memory for AI agents

Local-first. No telemetry, no cloud sync, no data leaves your machine. ViBo stores data ONLY on the user's device (a local .web file). It records only what the user explicitly provides, and every value is deletable. The single network call is a license check against https://wwwvibo.com.

ViBo is memory for AI agents, exposed as an MCP server so it works with any MCP client. Facts persist between sessions, semantic search returns only the relevant ones, and secrets never reach the LLM (encrypted L1/L2/L3).

License (important!)

This skill is commercial. Before first use, get a key:

One key = one machine. There is no built-in free key.

  • Explicit consent first: the agent must ask the user before storing any fact or thread history, and tell them what will be stored and how to delete it.
  • Stored locally only: a single .web file on the user's machine. Nothing is uploaded, shared, or synced.
  • Deletion: remove the local memory file, or use the forget/wipe commands (see the main ViBo docs). Secrets (L3) are encrypted (AES-256-GCM) and never sent to the LLM.
WhatWhereDelete
Memory facts (L1/L2/L3)local memory file (.web)remove the file / wipe
Thread historylocal thread file (.web)remove the file
License + client idnext to the skillsee EULA

Install

npm install -g @vibo-dev/vibo-mcp

Configure (Claude Desktop example)

{
  "mcpServers": {
    "vibo": {
      "command": "npx",
      "args": ["-y", "@vibo-dev/vibo-mcp"],
      "env": {
        "VIBO_API_KEY": "YOUR_VIBO_KEY"
      }
    }
  }
}

Tools

ToolDescription
memory_searchFind facts the user has stored (returns token savings)
memory_addStore a fact the user explicitly provides (dedup by exact match)
memory_usageLocal savings statistics
thread_memoryThread: add / compress / ask / context

Example

Agent: "What does client Anna prefer?" → memory_search("Anna preferences")• [L1] client-anna: Anna likes coffee without sugar💾 Saved 13,452 tokens (97.5%)

Honest numbers

  • Memory: 97.5% fewer tokens on 118 facts (grows with memory, 50–150× on 10K+).
  • Web search: 99.6% (measured 47,443 → 186 tokens).
  • Threads: −72%.
  • Secrets (L3): never reach the LLM — encrypted by design.

Related skills

Use when the agent needs persistent memory (L1/L2/L3), a living document archive (.vibo: pack documents, search by meaning, answer questions), web-search savings (compress articles up to 96%), thread memory (compress long conversations, restore details), live handoff (resume/save-state), or a privacy layer (mask secrets before they reach any LLM). Requires a valid ViBo license.

Local-first MCP memory backend and governance console for coding agents. Auto-organize, quarantine, supersede, and rollback shared memories across multiple a...

Install, configure, verify, or remove local-first Memkeeper memory for OpenClaw. Use when an OpenClaw user needs Memkeeper's local embedding and reranking mo...

Map of every agentmemory MCP tool, what each does, and its parameters. Use when choosing which memory tool to call, when a tool name or argument is unclear,...

Use when the owner hands the agent a multi-step task: grill the intent first (G1-G5 plan card, owner gate), then run it as an autonomous mission — restore context from ViBo memory, find and fix problems safely, iterate via paths A/B/C, save lessons. Optional Telegram notify/ask/report (OFF by default, runtime-warned; sends mission data only when the owner sets TELEGRAM_MISSION_TOKEN/CHAT). Built-in DEMO memory (100 facts) works without the ViBo CLI. Use ONLY with the user's explicit consent: missions save progress and lessons to local memory — tell the user what will be stored and how to delete it before starting.

1 installs

Scaffold, sanitize, or share an OpenClaw multi-agent memory system with a reusable workspace, memory-lancedb-pro configuration, role prompts, task-board conv...

13 installs