Persistent, read-only codebase memory for Claude Code; ask it instead of re-reading files.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
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, ask_live_memory, 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.

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 ask_live_memory 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.
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:
| per task | premium-model bill | all-in Β· DeepSeek-flashβ | all-in Β· Haiku | faster |
|---|---|---|---|---|
| Understanding-heavy (trace / comprehend) | β61% | β57% | β25% | ~22% |
| Hybrid (understand-then-edit: bug fixes + features) | β28% | β26% | β11% | ~11% |
| Pure edit / execution | ~break-even | ~break-even | ~break-even | ~0 |
Understanding-heavy work also offloads ~93% of the premium model's codebase-reading tokens (with lower
cost variance), and correctness never regressed on the hybrid tasks (12/12 passed with and without
it). DeepSeek-v4-flash matched Haiku's answer accuracy (98% vs 91% over 3 reps) at ~8Γ lower token
price; a local companion is β free, so all-in β the premium-model bill. Fully reproducible + audited
(human + Fable). Full numbers + methodology: benchmark/results/RESULTS.md.
β companion re-priced at DeepSeek-v4-flash rates (~8Γ cheaper than Haiku); exact for the understanding case, derived from the measured cost ratio for the hybrid case.
Lineage: Live Memory began as a feature of shofer.dev (Arkware's
parallel multi-agent coding platform), where sessions share an in-sync codebase memory. This is that
idea as a standalone Claude Code plugin β a fresh implementation, self-contained, with no
dependency on shofer. Part of the shofer Claude Code plugin family (with
slang-workflows).
Design: DESIGN.md Β· How it compares to Copilot/Cursor: COMPARISON.md Β· Testing: TESTING.md Β· Privacy: PRIVACY.md.
live-memory is an HTTP MCP server you run once (a singleton that serves every Claude Code session)
plus a plugin that registers ask_live_memory, the hooks, and the slash commands. Start the server
first β Claude Code only connects to it (it never spawns it), so if it isn't running you'll get a
connection error.
1 β Start the server (zero-config on a Claude subscription β Haiku; no API key needed):
2 β Install the plugin (inside a Claude Code session):
Ask your agent a whole-repo question β it'll call ask_live_memory instead of reading files.
/live-memory-stats shows accumulated knowledge + cost Β· /live-memory-config switches
model/provider Β· /live-memory-empty wipes memory Β· /live-memory-reset starts a workspace
over with its configured preload docs re-loaded. Providers, systemd, workspaces, and concurrency
are detailed below.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/live-memory)<a href="https://allmcps.com/mcp/live-memory"><img src="https://allmcps.com/api/badge/live-memory?style=directory" alt="Live Memory on AllMCPs" /></a>