Living Memory MCP Server

by viibe Your server? Claim it

answering

Living Memory is answering right now. Last checked 5 min ago. 54 installs a week from npm. Last commit 27 Aug 2026.

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

Installs per day peak 271 · avg 21 · -43% w/w

a month agotoday

Uptime history 17 days of history

17 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

645 ms

Response time

average over 24h

Installs / week

npm and PyPI

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.

File ships in the package but is absent from the source [пакет] src/brain.ts:1, [пакет] src/server.ts:1, [пакет] src/storage.ts:1

этот файл ставится пользователю, но в репозитории его нет

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.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "living-memory": {
      "url": "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

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

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URL	Transport	State	Latency	Checked
https://lme.viibe.to/mcp	streamable-http	needs key	638 ms	5 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.

67 installs/wk local only

Engrm

by dr12hes

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

91 installs/wk local only

Qovery MCP Server

by qovery

Deploy and manage your apps on Qovery

answering

Agentage Memory

by agentage

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

answering

Wontopos

by wontopos

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

483 installs/wk local only

microservices.sh

by microservices

MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.

59 installs/wk answering

Agentrank

by superlowburn

Google for AI agents. Gives your AI live search across 25,000+ scored MCP servers and tools.

35 installs/wk local only

Bourdon

by bourdon

Recognition-first cross-agent memory federation. One shared memory across all your agents.

379 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 645 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 with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.

Does Living Memory need an API key?

Yes. Every time we knock, Living Memory answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is Living Memory?

It answers our handshake in 645 ms on average, which is faster than 24% 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 54 times in the last week. Week over week that is -43%. 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?

Yes — it is published under the Apache-2.0 licence, written in TypeScript, 2 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.