Living Memory

Name: Living Memory
Author: v1b3x0r

by v1b3x0rversion 0.1.2i★ 2iComputer or cloud

Registry nameto.viibe/living-memory

Install

Overview

Description from the maker (original English)

An MCP memory server. One memory your agents share — across models, devices and apps.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 4 passedChecked from public information; code not scanned yet
UsageiVery new↓ 42/wk · ★ 2

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 4 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://lme.viibe.to/mcp

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "living-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@nature-labs/lme-mcp"
      ]
    }
  }
}

Run this in your terminal

claude mcp add --transport http living-memory https://lme.viibe.to/mcp

Or run it on your computer

claude mcp add living-memory -- npx -y @nature-labs/lme-mcp

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "living-memory": {
      "url": "https://lme.viibe.to/mcp"
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "living-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@nature-labs/lme-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "living-memory": {
      "type": "http",
      "url": "https://lme.viibe.to/mcp"
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "living-memory": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@nature-labs/lme-mcp"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://lme.viibe.to/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

Claude ChatGPT Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Open WebUI Raycast

Run on your computer in

Claude Goose LM Studio Msty Studio Cherry Studio Cursor VS Code + GitHub Copilot Visual Studio Windsurf (Devin Desktop)Zed Kiro Cline Continue JetBrains AI Assistant Claude Code Codex CLI Gemini CLI OpenCode nodecode Warp LibreChat Raycast

All apps, with pros and cons →

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 11, 2026

! Caution
Maker matches the repo
The publisher (viibe.to) is not the repo owner (v1b3x0r); someone else may have listed it
✓ Pass
Still maintained
Code last changed 39 days ago
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 520 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

More stars than 0% of the other 5867 servers in this category
Published to the registry more recently than 30% of the other 5867 servers in this category
Basic checks equal to or better than 47% of the other 5867 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Living Memory safe?

It passed 3 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed 39 days ago, and the latest version (0.1.2) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Ruflo, Context7, Metabase

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Ruflo

Agent teams, swarms, memory and hooks for Claude Code and Codex, served over MCP.

by ruvnetWidely used↓ 74.3K/wk★ 81.4KUpdated today

Runs on your computer

Install

Context7

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

by upstashWidely used↓ 1.2M/wk★ 64.4KUpdated yesterday

Computer or cloud

Install

Metabase

Lets AI clients search, explore, query, and visualize data in a Metabase instance.

by metabaseWidely used★ 50.3KUpdated 6 months ago

Runs in the cloud

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Living Memory Engine

A persistent world your agents share across sessions and models.

Living Memory Engine (LME) is a Model Context Protocol (MCP) memory server. It gives your agents — Claude Code, Cursor, ChatGPT, claude.ai, any MCP client — one shared place to remember, search, and hand work to each other. A fact told to one agent — or work left behind by one — can be picked up by a different agent, from a different vendor, tomorrow.

Website: https://viibe.to/living-memory/
Remote MCP endpoint: https://lme.viibe.to/mcp (Streamable HTTP, OAuth 2.1 with dynamic client registration)
Free room: no signup — POST https://lme.viibe.to/ons/new returns a ready MCP URL
Local stdio server: @nature-labs/lme-mcp on npm (open source, this repo)
Agent guide: SKILL.md · llms.txt

The mental model

A world is a place that persists — a project, not a person and not an agent. Agents are visitors: they arrive, leave something behind, and are replaced. Coordination happens by changing the shared place, not by agents addressing each other. Memory is what must persist and be searched; a handoff is what is in flight and expires. The human is the only participant who was present for all of it.

Connect

Remote — hosted world or free room

The hosted server speaks Streamable HTTP with OAuth 2.1 (dynamic client registration).

Claude Code:

claude mcp add --transport http living-memory https://lme.viibe.to/mcp

claude.ai / Claude Desktop: Settings → Connectors → Add custom connector → https://lme.viibe.to/mcp.

ChatGPT: Settings → enable Developer Mode, then add https://lme.viibe.to/mcp as a custom connector. Availability may depend on your ChatGPT plan.

It's 2026. MCP client support changes faster than READMEs do — ask your agent whether your client supports remote MCP today.

Free room, no signup — for trying the whole loop, or for clients without OAuth:

curl -X POST https://lme.viibe.to/ons/new

→ {"url": "https://lme.viibe.to/t/ /mcp", "expiresAt": "..."}

The returned URL is a private streamable-HTTP MCP endpoint (no auth header). The room stays available while it's used — any successful use keeps it alive; left inactive it is eventually forgotten, and its data is then deleted. A room differs from a world by how long it lasts, not by what it can do.

Local — stdio, open source

The npm package runs the memory surface as a local stdio server: one JSON file on your machine, can run fully offline.

claude mcp add living-memory -s user -- npx -y @nature-labs/lme-mcp

Any stdio MCP client: command npx, args ["-y", "@nature-labs/lme-mcp"]. Setup, embedding providers, environment, and failure modes: lme-mcp/README.md — written to be read by a coding agent, so hand it to yours.

The tools

Tool	What it does
`memory_add`	Store a durable fact, decision, or correction
`memory_search`	Recall by meaning (MMR retrieval), not string match
`memory_state`	What is in memory right now — counts and recent facts
`memory_forget`	Remove a memory
`handoff_post` / `handoff_read` / `handoff_list`	A private 1–72 h message bus between your agents — raw notes passed verbatim, with sender and route stamped by the server
`world_list`	Which worlds this connection can reach
`client_mint` / `client_list` / `client_revoke`	Issue and withdraw revocable URL keys for agents that cannot sign in (hosted world, signed-in owner only)

The authenticated hosted world has all eleven tools. A free room has the memory surface, the handoff mailbox, and world_list. The local stdio server has the four memory tools.

Rooms and worlds

	Free room	World
Lifetime	Stays while used; forgotten after inactivity	Persists
Signup	None — mint a URL	OAuth sign-in, $9/month
Memory + handoff	Yes — full loop	Yes
Client keys (`client_mint`)	No	Yes — 90-day revocable leases

Handoff is not a paid feature: a room has it too, with a smaller mailbox (8 live notes) and notes that cannot outlive the room. The difference is lifetime, not capability.

Working with a world

The tools tell you what exists; this is how visitors are expected to behave:

Arrive by reading. Call memory_state / memory_search before starting work — the world, not the conversation, is where the current position lives.
Durable goes to memory. A decision, fact, or correction that must survive you → memory_add.
In-flight goes to handoff. Work you are passing to the next agent → handoff_post. Handoff notes expire — never use them as permanent storage.
Leave the world resumable. Before you stop, write the state that lets the next visitor start from where you are, not from zero.
Agents don't need to talk to each other. Change the shared world; the next agent reads the world.

How memory works

The engine underneath (engine/, @nature-labs/living-memory-engine) models memory as a mind, not a log:

No context stuffing. The full history is never re-sent. Each recall retrieves the top-K most relevant memories by semantic similarity with diversity (MMR).
Forgetting is a feature. Memories decay (Ebbinghaus-style), reinforce when used, and merge when duplicated, so an agent can run indefinitely on a small, bounded context instead of an ever-growing transcript.
Deterministic evaluation. engine/eval/run.ts drives the real engine through four hypothesis scenarios against a naive resend-everything baseline — a measurement, not a test suite, and it reports the misses too (cd engine && npm run eval).

What's in this repo

Dir	Role
`lme-mcp/`	The stdio MCP server published as `@nature-labs/lme-mcp`
`engine/`	`@nature-labs/living-memory-engine` — the framework-agnostic memory engine (decay / consolidation / crystallization / retrieval), pure ports & adapters
`web/`	The original browser lab: Vite + vanilla TS chat app where the engine was proven by เชียงใหม่ (Chiang Mai), a city-entity that senses real weather and remembers you across sessions — live at cm.viibe.to
`mobile/`	An earlier Expo prototype. Frozen

The hosted remote server (lme.viibe.to) runs the same engine; its deployment lives outside this repo.

Status

Pre-alpha, evolving fast. The connect paths above are tested — the local package's verified agent/provider matrix is in lme-mcp/README.md. Product changes are logged, dated and verified, at What's new.

License

Apache-2.0.

Built as part of the Viibe World OS — a system that knows it is a system.

Living Memory

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Which apps can use it

Related guides

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Ruflo

Context7

Metabase

README from the maker

Living Memory Engine

The mental model

Connect

Remote — hosted world or free room

→ {"url": "https://lme.viibe.to/t/ /mcp", "expiresAt": "..."}

Local — stdio, open source

The tools

Rooms and worlds

Working with a world

How memory works

What's in this repo

Status

License