Living Memory MCP Server

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.

People who work with ebbinghaus decay, indexeddb and local first and want it reachable from Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-27 · ★ 2 · #153 OF 304 MAINTAINED MEMORY · VERIFIED 2026-09-18

Apache-2.0 · TypeScript servers · how we verify → /methodology

01 · Install Living Memory

Claude Code

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

Claude Desktop / Cursor / VS Code - add to config

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

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

https://lme.viibe.to/mcp

transport: streamable-http

endpoint alive - authentication required · probed 2026-09-18

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions · remote - your agent's requests go to lme.viibe.to

endpoint auth requires authentication - rejected our unauthenticated MCP initialize

license Apache-2.0 - declared in the repository

npm package @nature-labs/lme-mcp - the @nature-labs scope differs from the repo owner (v1b3x0r); confirm it's the project's official package

registry vendor namespace to.viibe - domain-verified with the official MCP registry

03 · Who maintains Living Memory

Living Memory is maintained by v1b3x0r. It's the only MCP server we track from this author; the repo dates to Dec 2025.

04 · Facts

repository: github.com/v1b3x0r/living-memory-engine
website: https://viibe.to/living-memory/
category: memory - ranked #153 of 304 actively-maintained memory servers as of 2026-09-18.
registry: to.viibe/living-memory (active, first published 2026-08-15)
packages: npm:@nature-labs/lme-mcp

05 · Living Memory FAQ

What is Living Memory?

Is Living Memory still maintained?

Yes - as of 2026-09-18, its last commit was 2026-08-27. We re-verify nightly.

How do I install Living Memory?

Run `npx -y @nature-labs/lme-mcp`. You can also paste the ready-made client config above.

Does Living Memory require authentication?

Yes - when we probed the endpoint on 2026-09-18, it rejected an unauthenticated MCP initialize; you'll need credentials to connect.

06 · Alternatives to Living Memory

Alternatives to Living Memory

Maintained memory servers if Living Memory isn't the fit.

Pairs well with

Servers that cover what Living Memory doesn't - only shown when the pairing reason fits the companion.

More memory MCP servers · Mif Tools · Shodh Memory · Superlocalmemory · Total Agent Memory · Memento

More TypeScript MCP servers · Valv · Nanostores MCP · Can LII (vaquill-ai) · Dokploy MCP · Vugola · see all