MCP.Market

Live Memory MCP server

by shofer-dev·io.github.shofer-dev/live-memory·v0.6.0·7 stars

Persistent, read-only codebase memory for Claude Code; ask it instead of re-reading files.

A86/100grade A
What users say
No reviews yet
Be the first
Safety scan
A86/100

full report

Adoption
Growing

7 stars18 downloads/wk

Reviews

Write one

Nobody has reviewed Live Memory yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Live Memory tools (3, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • ask_live_memory

    Ask the Live Memory about the codebase at `cwd`.

  • ask_live_memory_result

    Collect the result of an ask_live_memory_submit job by its job_id.

  • ask_live_memory_submitwrite action

    Submit a Live Memory question to run in the BACKGROUND and return a job_id immediately — use this instead of ask_live_memory when the query may be slow and you want to keep working, then collect the answer later.

Public scan report

scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it

no findings
  • Code scan22 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 55 days ago12/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Live Memory compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 72% of 48,255 servers
Tools
3
the typical server has 7
Tools that change things
33%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
7
more than 86% of 28,688 servers
Downloads a week
18
more than 5% of 12,191 servers with a package

What its tools let an agent do: 2 read · 1 change

Install Live Memory in Claude Code, Cursor or VS Code

claude mcp add live-memory -- uvx shofer-live-memory
Add to Cursor

What the publisher says

From the Live Memory repository's README, as published. We do not edit it. Read it on GitHub

██╗     ██╗██╗   ██╗███████╗
██║     ██║██║   ██║██╔════╝
██║     ██║██║   ██║█████╗
██║     ██║╚██╗ ██╔╝██╔══╝
███████╗██║ ╚████╔╝ ███████╗
╚══════╝╚═╝  ╚═══╝  ╚══════╝
███╗   ███╗███████╗███╗   ███╗ ██████╗ ██████╗ ██╗   ██╗
████╗ ████║██╔════╝████╗ ████║██╔═══██╗██╔══██╗╚██╗ ██╔╝
██╔████╔██║█████╗  ██╔████╔██║██║   ██║██████╔╝ ╚████╔╝
██║╚██╔╝██║██╔══╝  ██║╚██╔╝██║██║   ██║██╔══██╗  ╚██╔╝
██║ ╚═╝ ██║███████╗██║ ╚═╝ ██║╚██████╔╝██║  ██║   ██║
╚═╝     ╚═╝╚══════╝╚═╝     ╚═╝ ╚═════╝ ╚═╝  ╚═╝   ╚═╝
        always-up-to-date codebase memory for Claude Code · ask, don't re-read

Live Memory — Claude Code plugin

A cheap, always-on model that learns your repo — so your agent stops re-reading it. Live Memory runs a separate, cheap large-context model as a long-lived MCP server that accumulates knowledge of your codebase across sessions. Instead of re-reading the same files every session, your agent asks one read-only tool, asklivememory, the broad-understanding questions — "where is X, how does Y work, what calls Z" — and Live Memory answers in a way that bootstraps the primary agent to start doing productive work (e.g., edits). It learns passively from your agent's own reads and edits (teed via hooks — no extra reading) and stays current as the repo changes (modifications and deletions). Read-only and path-jailed (it can never edit, create, or run anything); zero-config on a Claude subscription (Haiku, no API key); the memory model is pluggable — point it at a local model or any OpenAI-compatible endpoint.

How it works

flowchart LR
  repo[("Your repo")]
  subgraph sessions["Claude Code sessions — premium model (many, over time)"]
    agent["Agent"]
  end
  agent -->|"reads / edits files"| repo
  agent -. "PostToolUse / FileChanged hooks<br/>tee file content — passive learning (free)" .-> lm
  agent ==>|"ask_live_memory(question, cwd)<br/>one read-only MCP tool"| lm
  lm ==>|"grounded answer — no file re-reading"| agent
  subgraph server["Live Memory — one MCP server per workspace (singleton)"]
    lm["Cheap / local large-context model<br/>+ accumulating context window<br/>append-only · neutral compaction to a ledger"]
    lm --> snap[("Local JSON snapshot<br/>persists across sessions")]
  end

Your agent reads or edits files as usual; hooks quietly tee that content to the server so it learns for free. When the agent needs to understand something, it asks asklivememory instead of re-reading — the server answers from its accumulated, per-workspace memory (or reads the code itself, read-only, if it hasn't seen it yet). One server serves every session and persists across sessions.

Benchmarks

A/B on a real repo, cost per task, run to completion. Cost is shown three ways: the premium (building) model's bill — what your expensive model spends, since the companion runs on a cheap or local model — and all-in, also counting the companion's own cost on DeepSeek-v4-flash or Haiku:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Live Memory: common questions

Is Live Memory MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the Live Memory safety report
How do I install Live Memory?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Live Memory need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Live Memory maintained?
The last commit was 95 days ago (2026-08-01). The latest release is v0.6.0.
What can I use instead of Live Memory?
Servers from other publishers that do the same job: Codebase Memory MCP server, Computer MCP server and State Memory MCP server. Compare all Live Memory alternatives.
How does Live Memory compare with other MCP servers?
safety score 86/100 (higher than 72% of 48,255 servers); tools 3 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Live Memory

Same job from other publishers: the closest match first, then the best rated.

All Live Memory alternatives →
  • Codebase Memory
    Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
    C
  • Computer
    A private persistent computer: files that survive between runs, a bash shell and JavaScript.
    A
  • State Memory MCP
    Persistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.
    A
  • Knowl
    Persistent memory for AI agents, for code, research and everyday life. Stale facts retire.
    A