Усильте агента
Собственный URL издателя. Не эндпоинт PlugMCP.
Host a copy with our keys and logs.
https://lme.viibe.to/mcpКнопка Claude выше открывает Claude с заполненными названием и URL. Подтвердить добавление всё равно нужно там.
claude mcp add --transport http to.viibe-living-memory https://lme.viibe.to/mcpRun in a terminal.
{ "mcpServers": { "to.viibe-living-memory": { "command": "npx", "args": [ "-y", "mcp-remote", "https://lme.viibe.to/mcp" ] } }}claude_desktop_config.json
Удалённый URL или команда на вашем компьютере? Чем различаются два способа установки
Запустить на PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
ЗапускОт издателя
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.
An MCP memory server. One memory your agents share — across models, devices and apps.
https://lme.viibe.to/mcp (Streamable HTTP, OAuth 2.1 with dynamic client registration)POST https://lme.viibe.to/ons/new returns a ready MCP URL@nature-labs/lme-mcp on npm (open source, this repo)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.
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/<token>/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.
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 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.
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.
The tools tell you what exists; this is how visitors are expected to behave:
memory_state / memory_search before starting work — the world, not the conversation, is where the current position lives.memory_add.handoff_post. Handoff notes expire — never use them as permanent storage.The engine underneath (engine/, @nature-labs/living-memory-engine) models memory as a mind, not a log:
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).The hosted remote server (lme.viibe.to) runs the same engine; its deployment lives outside this repo.
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.
Apache-2.0.
Built as part of the Viibe World OS — a system that knows it is a system.
An MCP memory server. One memory your agents share — across models, devices and apps.
{ "mcpServers": { "to.viibe-living-memory": { "url": "https://lme.viibe.to/mcp", "headers": {} } }}Инструменты
Списка инструментов пока нет. У удалённых серверов он появляется после первой проверки состояния.
FAQ
Скопируйте на этой странице конфигурацию http для Cursor, Claude Desktop, Claude Code или VS Code. Она использует установку издателя, а не прокси PlugMCP.
В этой записи не указано обязательных переменных окружения.
Living Memory доступен по HTTP.
Последняя проверка: 2026-11-10. An MCP memory server. One memory your agents share — across models, devices and apps.