mcpbeat Sign in

Vibo Memory MCP Server

local only

Vibo Memory runs on your own machine — the client starts it, so there is no endpoint to ping. 48 installs a week from npm. Last commit 13 Sep 2026.

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

Installs per day peak 457 · avg 47 · +20% w/w
a month agotoday
48
Installs / week
npm · @vibo-dev/vibo-mcp
1
Stars
0 open issues
13 Sep 2026
Last commit
0 releases in 90 days
MIT
License
Python

What the code does

We read the source, 11 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Runs an external command vibo-selfdeed/lib_vibo.py:183
            return subprocess.run(
Sends data to a third-party sink vibo-selfdeed/telegram_mission.py:35
API = "https://api.telegram.org/bot"

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add vibo-memory -- npx -y @vibo-dev/vibo-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "vibo-memory": {
      "args": [
        "-y",
        "@vibo-dev/vibo-mcp"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.vibo-memory]
command = "npx"
args = ["-y", "@vibo-dev/vibo-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "vibo-memory": {
      "args": [
        "-y",
        "@vibo-dev/vibo-mcp"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "vibo-memory": {
      "args": [
        "-y",
        "@vibo-dev/vibo-mcp"
      ],
      "command": "npx"
    }
  }
}

Alternatives to Vibo Memory

same job, measured the same way
Vibo MCP
by vnbochkarev-netizen

Persistent memory for AI agents: L1/L2/L3, web compression, threads.

local only
Memstack
by isiomac

MCP server for persistent, searchable memory for AI agents.

49 installs/wk local only
MCP Memory
by infoinlet-marketplace

Persistent searchable memory for AI agents — save/get/search across sessions, tags.

20 installs/wk local only
Mem0
by mem0ai

Persistent memory for AI agents: add, search, update, and delete long-term memories.

answering
Iranti
by nfemmanuel

Persistent, shared memory for AI agents — facts, checkpoints, semantic search.

29 installs/wk local only
Context Mem
by jubakitiashvili

Persistent memory for AI agents — 98%+ retrieval recall, 99% token savings, 44 tools

75 installs/wk local only
Ace Memory
by rudedoggg

Persistent memory for AI agents. Semantic search, memory graph, W3C DID identity.

answering
Goldhold
by jerrysrodz

Persistent memory for AI agents. Search, store, and recall across sessions.

29 installs/wk answering

Vibo Memory — questions

Answers built from our own checks of this server.

Why is there no uptime for Vibo Memory?
Vibo Memory runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @vibo-dev/vibo-mcp was installed 48 times last week.
How do I connect Vibo Memory?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @vibo-dev/vibo-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Vibo Memory?
The npm package @vibo-dev/vibo-mcp was installed 48 times in the last week. Week over week that is +20%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Vibo Memory open source?
Yes — it is published under the MIT licence, written in Python and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.