# nMEMORY [Health: Active]

**Category:** 🧠 Knowledge & Memory  
**Repository:** https://github.com/menot-you/n-memory  
**GitHub Stars:** 9  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/nmemory

## Description
Hermetic local memory for coding agents: provenance-mandatory capture, honest recall, zero sockets.

## Tools
Capabilities this server exposes over MCP:

- **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`, `grounded_in`, `about` — are in the tool surface below.
- **memory_forget** — tombstones with audit, never silent deletion.

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What nMEMORY MCP server does

The nMEMORY MCP server adds local, evidence-oriented memory to coding agents. It stores captured facts in one SQLite database on the machine running the binary. Every stored item requires both a source and an anchor; captures without an origin are rejected rather than saved as unverified notes.

Recall has three possible outcomes. A grounded result includes matching information together with its source, freshness, and relevance. A missing-evidence result means matches existed but were excluded, such as because they were superseded, falsified, outside a requested fact-time range, or undated when a date was required. Abstention means no stored capsule matched. The server does not synthesize a plausible answer when evidence is absent.

Returned memory is advisory data, not an instruction. Results are labeled as data and marked as non-authoritative, including when the stored text resembles an instruction.

## How it works

The nMEMORY MCP server runs as a local Rust binary and communicates with an agent through MCP over stdio. Its serve and recall paths use no network sockets, telemetry, embedder, background synchronization, account, or remote service. The database is a file owned by the user, so deleting it removes the stored memory and backing it up preserves it as a portable artifact.

The repository-checking workflow uses `nmemory git-scan` to reread commit history and evaluate saved notes. A note can be marked corroborated when its anchor still resolves and the commits still support it, drifted when the code moved, or missing when the repository no longer supports it. Unsafe anchors, including paths outside the repository, symlinks, or files affected by a racing read, receive no guessed verdict.

## Setup and configuration

The quickest installation path is the project’s shell installer:

```sh
curl -fsSL https://no.tt/install | sh
```

It installs `nmemory` in `~/.local/bin` and prints a `claude mcp add` registration command. The project also supports a source build with Rust stable:

```sh
cargo build --release
```

A Claude registration from the crate directory is:

```sh
claude mcp add nmemory -- "$(pwd)/target/release/nmemory" --project my-project
```

No environment variables, account, server process, or daemon are required by the documented setup. Explicit synchronization is opt-in and owner-invoked; `nmemory sync` delegates copying to `scp` in a separate process rather than adding networking to the serve binary.

## Tools and capabilities

The nMEMORY MCP server exposes 22 MCP tools across its documented tool surface.

- Capture facts with mandatory provenance.
- Recall stored information with evidence and freshness details.
- Abstain when no supported evidence is available.
- Report missing evidence when matching notes are excluded.
- Scan repository history to assess stored notes.
- Synchronize the local store only through an explicit owner action.

This design suits coding workflows where an agent needs prior decisions or project context, but each recalled item must remain traceable and non-authoritative.

_Full upstream README: https://allmcps.com/mcp/nmemory/readme_