Live Memory
Persistent, read-only codebase memory for Claude Code; ask it instead of re-reading files.
Connector by shofer-dev · GitHub account verified by the MCP Registry
Chalk Labs
Need help deploying Live Memory?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Pick your client. Read the repository before you give any tool access to your data.
No install instructions from the source yet. Check the repository for setup steps.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.
- Tools
- 8 read · 0 write · 0 delete · 1 not yet classified
- Secrets
- None asked for
- Install scripts
- Not scanned yet
- Runs as
- Python package
Tools by what they do 9
Read from the source code; the running server may list different tools.
Read 8 · Look things up without changing anything.
ask_live_memoryask_live_memory_resultfind_pathsget_changed_filesgit_searchGlobGrepRead
Not yet classified 1 · We could not tell from the name and description.
ask_live_memory_submit
Files it touches
- Any path the agent passes to its tools
Tools (9)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
ask_live_memoryAsk the Live Memory about the codebase at `cwd`. The Live Memory is a persistent, read-only companion that accumulates knowledge of *this* repository across questions and sessions. It runs a separate, cheap, large-context model and explores on its own (read, grep, glob, git history), so it can answer "where is X / how does Y work / what calls Z / what's the convention for W" without you loading files into your own context — and it often already knows the answer from earlier questions. It returns a best-effort answer within its server-configured time budget: grounded in the actual code, but te…
ask_live_memory_resultCollect the result of an ask_live_memory_submit job by its job_id. Returns the full answer (with metadata) when ready; "[running] …" if it is still working (do other work and poll again); or an error if the job failed or the id is unknown/expired. A successful/failed result is consumed once (collect it again only after a new submit).
ask_live_memory_submitSubmit 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. Returns a job_id. Do other work, then call ask_live_memory_result with that job_id to fetch the answer (it reports "[running]" until ready). Same answer quality as ask_live_memory; same args (see that tool for `cwd` rules — absolute repo root — and `max_answer_tokens`).
find_pathsWalk the directory tree and list entries (files and/or directories) under a path, filtered like the `find` CLI — by name pattern, entry type, and depth. Use this to explore structure or list directories; use Glob when you just want files matching a glob.
get_changed_filesFiles changed in the working tree (git status --porcelain).
git_searchInspect git commit history. Filter by commit-message text (query) and/or a file/dir path, and optionally include the patch (diff) for each commit. With no query and no path, returns the most recent commits.
GlobFind files by glob pattern (relative to the workspace root). Returns matching paths, sorted. Use find_paths instead when you need directories, a type/depth filter, or to enumerate the tree.
GrepSearch file contents with ripgrep (regex). By default returns matching 'file:line:text'; set output_mode to 'files_with_matches' for paths only, or 'count' for per-file match counts.
ReadRead a slice of a UTF-8 text file, returned with line numbers. The path is relative to the workspace root.
Signals
- Stars
- 7
- Forks
- 0
- Open issues
- 0
- Weekly downloads
- 31
- Last commit
- Aug 1, 2026 (3 months ago)
- Last release
- Jul 17, 2026 (3 months ago)
- Last package publish
- Jul 17, 2026 (3 months ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.shofer-dev/live-memory- Version
- 0.6.0
- Auth
- No auth
- Packages
- pypi shofer-live-memory
- License
- Apache-2.0
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
More from shofer-dev
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get Live Memory running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
Live Memory MCP server. Agent Mart. https://agentmart.dev/connectors/shofer-dev-live-memory (last updated 2026-10-24)