Limpet
Persistent, code-anchored memory for AI coding agents that flags itself when code changes
- Pricing
- Open source
- Platforms
- macOS, Linux, Windows
- Version
- 0.17.0
- Listing updated
- today
Similar MCP servers
About Limpet
Limpet is an open-source MCP server for developer tools. It is available on macOS, Linux, Windows, CLI and vscode.
The README says limpet stores what an agent learns about a codebase, such as decisions, verified facts, failed approaches and gotchas, and keeps it across sessions. Each memory is anchored to a normalized AST hash of the code it describes. Renames and file moves are followed, while real edits flip the memory to stale with a reason attached, and reverting the code heals it.
It ships as a single Rust binary that stores everything in one SQLite file and speaks standard MCP. The README states that indexing, recall and the UI make no network calls, with the sole exception of the explicit update command. Recall is token-budgeted, and every response carries metadata about what was matched, omitted and stale.
The project is aimed at solo developers using Claude Code, teams that share a committed memory export, and maintainers who want to record why odd code exists. The README notes that throwaway repositories and teams without AI agents gain little from it.
Tools this server provides (6)
Taken from the project documentation; the running server may differ.
- recall
- Task description in, token-budgeted ranked memory pack out.
- remember
- Store a fact, decision, episode, insight or intent anchored to code.
- map
- Structural outline of a file or symbol plus attached memories.
- affected
- Symbols, memories and decisions touched by the uncommitted diff.
- verify_queue
- Verified facts whose anchored code has changed.
- admin
- Index, status, forget, archive, export, import, ledger, reverify and consolidate operations.
What it does
- Code-anchored memories
- Memories attach to AST hashes of functions, files and symbols rather than line numbers or paths.
- Automatic staleness detection
- Edits mark dependent memories stale with the reason, and reverts restore them to active.
- Six MCP tools
- Recall, remember, map, affected, verify_queue and admin cover storage, lookup and maintenance.
- Local-only storage
- A single SQLite store per repository with no telemetry, accounts or cloud sync.
- Token savings ledger
- Recalls are priced against the file reads they replace, viewable through the stats command.
- Knowledge graph UI
- A local web view on 127.0.0.1 shows memories, anchors and their health.
- Team export and import
- Memories export to a JSONL file that can be committed and imported by teammates, with guarded validation.
Good for
- Recalling why a batch size or workaround exists without re-reading the code each session
- Flagging documented decisions that a pending diff may put at risk
- Sharing onboarding knowledge in a repository that updates when the code changes
- Keeping a record of refactors that were tried and rolled back
- Seeding memory from an existing MEMORY.md or CLAUDE.md notes file
Pricing
Open source
MIT licensed and free to use; no paid plan is mentioned.
Limpet FAQ
Does limpet send data over the network?
The README says indexing, recall, memory and the UI make no network calls. The only networked command is limpet update, which must be run explicitly.
Which platforms are supported?
The README lists prebuilt binaries for Apple Silicon macOS, x86_64 Linux and x86_64 Windows, and says other platforms can build with cargo install.
How does it know a memory is out of date?
Each memory is anchored to a normalized AST hash of its code. When that hash changes at the anchored symbol or file, the memory is marked stale with a reason such as body_edited or file_edited.
Where is the data stored?
The README says data lives under ~/.local/share/limpet/, with one SQLite store per repository.
Is Limpet free?
Yes. Limpet is open source, so you can use and self-host it for free.
What are the best alternatives to Limpet?
The closest alternatives to Limpet are Memoria — Deterministic AI Memory & Code Intelligence MCP, memry, Total Agent Memory, Remem and Memro.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.