Persistent engineering memory for AI coding agents. Survives refactors, knows when it is stale.
Persistent engineering memory for AI coding agents. Survives refactors, knows when it is stale. The limpet mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 6 defined tools rather than through you.
the anchor lifecycle, real output: recall answers instantly, an edit flips the memory stale, a revert heals it
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
Everything the assistant can do here goes through one of these:
recall — Task description in, token-budgeted ranked memory pack out. Stale and contradicted items are always flagged, never hidden. Verified facts outrankremember — Store a memory: fact, decision, episode, insight, or intent. Anchor it to code. Attach evidence to make it verified. A near-identical body on themap — Structural outline of a file or symbol plus every memory attached to it. For a symbol target it also returns lineage (ancestors, descendantsaffected — What does my uncommitted diff touch: symbols, memories now at risk, and decisions constraining the code being editedverify_queue — Verified facts whose anchored code changed, each with the exact command that originally proved itadmin — index, status, forget, archive / restore, export / import (guarded), ledger / ledger_reset (the savings receipt). Archive shelves a memory withoutThis sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Limpet's toolset — recall, remember, map and 3 more — is a fair guide to whether it matches your workflow. It is maintained by KSym04; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| recall | Task description in, token-budgeted ranked memory pack out. Stale and contradicted items are always flagged, never hidden. Verified facts outrank unverified claims at equal relevance; an item without a source field is an |
| remember | Store a memory: fact, decision, episode, insight, or intent. Anchor it to code. Attach evidence to make it verified. A near-identical body on the same anchor is refused (naming the existing id to supersede; force: true o |
| map | Structural outline of a file or symbol plus every memory attached to it. For a symbol target it also returns lineage (ancestors, descendants, callers) with each edge labeled unique/ambiguous/unresolved. Code and knowledg |
| affected | What does my uncommitted diff touch: symbols, memories now at risk, and decisions constraining the code being edited. |
| verify_queue | Verified facts whose anchored code changed, each with the exact command that originally proved it. |
| admin | index, status, forget, archive / restore, export / import (guarded), ledger / ledger_reset (the savings receipt). Archive shelves a memory without deleting it: hidden from recall while its staleness keeps tracking the co |
A knowledge graph your assistant keeps between sessions — entities, relations and observations that persist.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
A structured scratchpad for hard problems — stepwise reasoning with revisions, branches and visible logic.
Symbol-level code navigation, refactoring and memory for coding agents — the IDE brain your assistant has been missing.
Chat with your second brain — search, read and write vault notes through the Local REST API.