MCP.Market

Nuzo Memory MCP server

by fabionfsc·io.github.fabionfsc/nuzo-memory·v1.2.0·2 stars
No reviews yet

Local-first, auditable memory for MCP-compatible AI agents with explicit writes and SQLite storage.

C69/100grade C
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
C69/100

full report

Adoption
Growing

2 stars35 downloads/wk

Reviews

Write one

Nobody has reviewed Nuzo Memory yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Nuzo Memory tools (19, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • memory.audit

    List bounded store-wide Nuzo audit events without memory content.

  • memory.challenge

    Mark one memory as valid, needing review, stale, incorrect, or superseded. This never deletes memory content.

  • memory.confirm_capture

    Apply the user's explicit decision after the host displayed a memory.suggest_capture draft. confirm=true is the host's attestation of that interaction; Nuzo does not persist or cryptographically bind drafts.

  • memory.doctor

    Report the local Nuzo MCP memory environment.

  • memory.export

    Export local Nuzo memories as a versioned JSON document and append an export audit event.

  • memory.forget

    Archive or delete a local Nuzo memory.

  • memory.forget_many

    Preview or apply a filtered bulk archive/delete operation.

  • memory.history

    List audit events for one Nuzo memory ID.

  • memory.import

    Import local Nuzo memories from a versioned JSON document.

  • memory.list

    List local Nuzo memories.

  • memory.recall

    Recall relevant local Nuzo memories.

  • memory.recall_hook

    Prototype read-only recall entrypoint for host lifecycle hooks. It never captures or creates memories.

  • memory.relatewrite action

    Create an explicit, manual relation between two local Nuzo memories.

  • memory.relations

    List explicit relations for one local Nuzo memory.

  • memory.remember

    Store a local Nuzo memory only when the user explicitly requested this exact write. For inferred capture, call memory.suggest_capture, display its returned draft, obtain the user's decision, then call memory.confirm_capture.

  • memory.show

    Inspect one local Nuzo memory with relations and recent audit events.

  • memory.suggest_capture

    Validate an inferred capture draft without writing. Display the returned draft to the user; only after their explicit decision may the host call memory.confirm_capture with the final approved fields.

  • memory.unrelatewrite action

    Remove an explicit memory relation without deleting either memory.

  • memory.updatewrite action

    Update a local Nuzo memory.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

1 high
  • Code scan15 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancerepository archived0/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highRepository is archivedmaint.archived
Overall 69/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Nuzo Memory compares

Against every graded Databases MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
69/100
higher than 26% of 802 Databases servers
Tools
19
the typical Databases server has 8
Tools that change things
16%
typical: 10%. Fewer write tools means less an agent can break
GitHub stars
2
more than 60% of 602 Databases servers
Downloads a week
35
more than 21% of 328 Databases servers with a package

What its tools let an agent do: 15 read · 1 create · 3 change

Install Nuzo Memory in Claude Code, Cursor or VS Code

Runs npx -y @nuzo/memory-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add nuzo-memory -- npx -y @nuzo/memory-mcp
Add to Cursor

What the publisher says

From the Nuzo Memory repository's README, as published. We do not edit it. Read it on GitHub

Nuzo

Local-first, auditable memory for AI agents. Durable context for Codex, Claude Code, and MCP-compatible hosts—without turning memory into hidden state.

Install · 60-second demo · Why Nuzo? · Security · MCP contract

Nuzo keeps scoped memories in local SQLite. Agents can recall bounded context across sessions, while you retain a CLI and public MCP contract to inspect, update, export, archive, or delete every record. Inferred memories remain drafts until you confirm them; recalled content remains untrusted data.

[!IMPORTANT]

Nuzo 1.2.0 is the final planned release. The repository becomes read-only

after publication, and no ongoing maintenance or security response is

promised. Published packages remain available for reproducible use and

forking. See the end-of-maintenance notice.

Quick Start

Use Node.js 22 LTS or 24 LTS with npm 10 or newer:

npm install --global @nuzo/memory@1.2.0
nuzo setup

nuzo setup detects Codex and Claude Code, previews host changes, and asks before writing configuration. To evaluate Nuzo without configuring a host or touching your normal store, run the disposable 60-second demo.

Two read-only recall hooks are expected: SessionStart and UserPromptSubmit. They do not write memory.

Non-interactive setup and upgrade commands

nuzo setup --codex --yes
nuzo setup --claude-code --yes
nuzo setup --all --yes
nuzo update --yes
nuzo memory manage

The Memory Loop

Automatic host hooks only recall. Explicit requests can write directly; inferred capture uses a visible suggest-and-confirm flow. The same core policy applies through the CLI, MCP server, and supported host integrations.

nuzo memory remember "The demo project uses SQLite." \
  --kind project_decision --tag demo
nuzo memory recall "demo storage"

Proof, Not Promises

Inspect the memory model, MCP tool contract, trust boundary, and release checklist.

When Nuzo Fits

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Nuzo Memory: common questions

Is Nuzo Memory MCP server safe?
With care: it is graded C, so read the findings first (69/100). Read the Nuzo Memory safety report
How do I install Nuzo Memory?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Nuzo Memory need an API key?
No secret keys are declared. It reads 4 settings from the environment.
Is Nuzo Memory maintained?
The last commit was 81 days ago (2026-08-14). The latest release is v1.2.0.
What can I use instead of Nuzo Memory?
Servers from other publishers that do the same job: Remem MCP server, open-memex MCP server and SAME - Stateless Agent Memory Engine MCP server.
How does Nuzo Memory compare with other Databases MCP servers?
safety score 69/100 (higher than 26% of 802 Databases servers); tools 19 (the typical Databases server has 8); tools that change things 16% (typical: 10%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Nuzo Memory

Same job from other publishers: the closest match first, then the best rated.

  • Remem
    Local-first automatic memory for Claude Code and Codex: capture, distill, recall from SQLite.
    B
  • open-memex
    Local-first memory for AI coding agents — Markdown + SQLite FTS5, shared across editors via MCP.
    B
  • SAME - Stateless Agent Memory Engine
    Persistent memory for AI coding agents. Local-first SQLite + vector search. 17 MCP tools.
    B
  • remem-mcp — Local-first MCP Memory + CodeGraph + Wiki
    Local-first memory for AI coding agents. Memory + CodeGraph + Wiki in one SQLite file.
    B
  • LoreConvo
    Local-first persistent session memory for Claude Code and other agents. SQLite + FTS5, no cloud.
    B