mcpbeat Sign in

Living Memory MCP Server

by viibe Your server? Claim it
answering

Living Memory is answering right now. Last checked 10 min ago. 47 installs a week from npm. Last commit 2 Oct 2026.

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

Installs per day peak 90 · avg 10 · +104% w/w
a month agotoday
Uptime history 79 days of history · worst day 92%
79 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
689 ms
Response time
average over 24h
47
Installs / week
npm and PyPI

Nothing serious here today

Today is the operative word: we check Living Memory every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add living-memory --transport http https://lme.viibe.to/mcp
Settings → Connectors → Add custom connector, then paste this address
https://lme.viibe.to/mcp
~/.codex/config.toml
[mcp_servers.living-memory]
url = "https://lme.viibe.to/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "living-memory": {
      "url": "https://lme.viibe.to/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "living-memory": {
      "type": "http",
      "url": "https://lme.viibe.to/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://lme.viibe.to/mcp streamable-http sign-in 635 ms 10 min ago

Alternatives to Living Memory

same job, measured the same way
Epiphany
by gatsv-tech

One private, local memory your AI tools share. Cross-model, on-device, never lose a session.

41 installs/wk local only
Engrm
by dr12hes

Shared memory across devices, sessions, and agents for OpenClaw, Claude Code, and Codex.

1 048 installs/wk local only
Cross-Agent Memory
by indamices

Local-first shared memory for AI coding agents: one searchable store, served over MCP. MIT.

local only
Qovery MCP Server
by qovery

Deploy and manage your apps on Qovery

answering
Memlo
by memlo

Hosted memory for AI agents over MCP. One memory shared by all your agents.

answering
M1K3
by m1k3

Private memory, documents, voice and a local LLM for your agents, served by a Mac app on-device.

local only
Agentage Memory
by agentage

One memory, every AI. A shared, user-owned markdown memory your AI clients read and write over MCP.

answering
W
Wontopos
by wontopos

Wontopos (WOS) long-term memory (beta) - one memory across Claude Code, Cursor, and your agents.

147 installs/wk local only

Living Memory — questions

Answers built from our own checks of this server.

Why is there no tool list for Living Memory?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Living Memory working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 689 ms. The bar chart above shows every period we have measured.
How do I connect Living Memory?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Living Memory?
No API key is involved. Living Memory answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Living Memory?
It answers our handshake in 689 ms on average, which is faster than 14% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Living Memory?
The npm package @nature-labs/lme-mcp was installed 47 times in the last week. Week over week that is +104%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Living Memory open source?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript, 2 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at lme.viibe.to, which runs on its operator's own terms.