Hermetic local memory for coding agents: provenance-mandatory capture, honest recall, zero sockets.
Connect NMEMORY to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Hermetic local memory for coding agents: provenance-mandatory capture, honest recall, zero sockets. The nmemory mcp server is what makes that connection.
Your coding agent forgets you between sessions, so you spend every morning re-explaining decisions it was there for. Bolt a memory onto it and you usually trade that for something worse: asked a question it has nothing solid for, the memory hands back something plausible anyway, and your agent goes and edits your code with it.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
memory_ingest — capture with a birth certificate: no source + anchor, no storagememory_retrieve — recall as evidence: grounded, missing_evidence, or an honest abstainmemory_digest — session-start projection: what you know, what's ready, what's blockedmemory_relate — the five edges you reach for daily, out of nine declared: supersedes, derived_from, witnesses, blocks, and falsifies (a disproven fact stopsmemory_forget — tombstones with audit, never silent deletionmemory_extract — text → candidate memories over the closed 10-kind set; advisory, stores nothingmemory_classify — kind / scope / authority / taint labels; optionally persisted as a sidecarmemory_import — one-shot import of native sources (CLAUDE.md, AGENTS.md, memory dirs); born taintedmemory_get — one full capsule by id, with GET-only fact time, relations,memory_list — compact index with project fencesmemory_bootstrap — cold-start pack: your constraints FIRST (never capped), the one next action, decisions, traps — in ≤1500 tokensmemory_alias — teach recall synonyms the store then honorsPlenty of knowledge and memory servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. NMEMORY's toolset — memory_ingest, memory_retrieve, memory_digest and 11 more — is a fair guide to whether it matches your workflow. It is maintained by menot-you; 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 |
|---|---|
| memory_ingest | capture with a birth certificate: no source + anchor, no storage. |
| memory_retrieve | recall as evidence: grounded, missing_evidence, or an honest abstain. |
| memory_digest | session-start projection: what you know, what's ready, what's blocked. |
| memory_relate | the five edges you reach for daily, out of nine declared: supersedes, derived_from, witnesses, blocks, and falsifies (a disproven fact stops grounding recall, but the evidence stays). The other four — proposes, part_of, |
| memory_forget | tombstones with audit, never silent deletion. |
| memory_extract | text → candidate memories over the closed 10-kind set; advisory, stores nothing |
| memory_classify | kind / scope / authority / taint labels; optionally persisted as a sidecar |
| memory_import | one-shot import of native sources (CLAUDE.md, AGENTS.md, memory dirs); born tainted |
| memory_get | one full capsule by id, with GET-only fact time, relations, |
| memory_list | compact index with project fences |
| memory_bootstrap | cold-start pack: your constraints FIRST (never capped), the one next action, decisions, traps — in ≤1500 tokens |
| memory_alias | teach recall synonyms the store then honors |
| memory_vector | attach caller-fed embeddings (optional cosine lane; no embedder inside) |
| memory_visual | deterministic Mermaid projections (dag / relations / tiers / sessions), plus an MCP Apps view |
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.