Log inSubmit server
NMEMORY logo

NMEMORY

Local, provenance-required memory for coding agents with evidence-based recall and abstention.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install NMEMORY

Pick your client, then add it in one click or paste the config.

No confirmed install command yet

We only publish a config when the install details come from the project itself — its README, its docs, or a verified owner. We haven’t found those for nMEMORY, and we’d rather show nothing than a guess you’d paste into your client.

Open setup steps on GitHub

Overview

The nMEMORY MCP server gives coding agents local memory backed by a single SQLite file and exposed over MCP stdio. It stores facts only when each has a source and anchor, then returns recalled information with provenance, freshness, and relevance or explicitly abstains. A repository scan can compare stored notes with commit history and classify them as corroborated, drifted, or missing. Reach for it when session continuity matters but unsupported or fabricated recollections are unacceptable.

Use cases

  • Capture project decisions with source anchors
  • Recall prior coding context with provenance
  • Check stored notes against repository history
  • Keep agent memory on a local SQLite file

Key features

  • Provenance-required memory capture
  • Evidence-based recall with abstention
  • Local SQLite storage
  • Repository history self-checking
  • MCP stdio transport
  • Explicit opt-in synchronization

Tools5

What NMEMORY lets your agent do. Expand a tool for its parameters.

Self-reported~149 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars9Stargazers on the source repository.
Last commit2mo agoMost recent push to the default branch.
Tools exposed5Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How NMEMORY works

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:

Terminal
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:

Terminal
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.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about NMEMORY

nMEMORY is an MCP server that connects coding agents over local MCP stdio to a SQLite memory file. Its main tools support provenance-required learning, evidence-based recall, repository git scanning, and explicit synchronization through scp. It abstains when stored evidence is missing and labels returned memory as advisory rather than authoritative.

Install it with `curl -fsSL https://no.tt/install | sh`. The installer places `nmemory` in `~/.local/bin` and prints a Claude registration command. Alternatively, build it from source with `cargo build --release` using Rust stable.

Yes, it can be used with Cursor through its standard MCP stdio configuration. The README explicitly shows Claude registration, while the server exposes a conventional stdio MCP interface rather than requiring a client-specific network service.

It avoids fabricated memories by requiring a source and anchor for every captured fact and limiting recall to three outcomes: grounded, missing_evidence, or abstain. When no supported evidence exists, it returns an abstention instead of synthesizing an answer.

Yes, `nmemory git-scan` checks stored notes against repository commits. It can classify notes as corroborated, drifted, or missing, and records no verdict when an anchor cannot be resolved safely.

Related MCP servers

All in Knowledge & Memory All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNMEMORY AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/nmemory?style=directory)](https://allmcps.com/mcp/nmemory)
HTML Embed
<a href="https://allmcps.com/mcp/nmemory"><img src="https://allmcps.com/api/badge/nmemory?style=directory" alt="NMEMORY on AllMCPs" /></a>