Vibo Memory

io.github.vnbochkarev-netizenPublished by GitHub account vnbochkarev-netizenv0.1.2Updated Oct 30, 2026

Memory for AI agents: persistent L1/L2/L3, web-search savings, thread memory.

The publisher's own server: Memory.fit

Overview

AI-generated overview

Vibo Memory is a local MCP server that gives AI assistants persistent L1/L2/L3 memory, thread memory and web-search savings.

What you can do
  • Provide persistent memory for AI agents across three tiers (L1/L2/L3).
  • Keep thread-level memory so context carries across conversations.
  • Reduce repeated web-search work through search savings.
  • No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Worth considering when you want an assistant to remember information between sessions or threads instead of restating context, and when repeated web lookups are a cost you want to cut.
Requirements
Runs as a local process over stdio, installed from the npm package @vibo-dev/vibo-mcp, so Node.js is needed. Requires a ViBo license key supplied in the VIBO_API_KEY environment variable; a free trial is mentioned. Desktop only.
Before you install
You must supply a ViBo license key (VIBO_API_KEY) to a third-party service; treat it as a secret. Memory persistence means stored conversation content may be retained and sent to the provider. No tools are listed, so review what it writes or shares before use.

Installation

In SourceWeft

  1. Open Vibo Memory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

35% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

Other Memory integrations