Nuzo Memory

io.github.fabionfscPublished by GitHub account fabionfscv1.2.0Updated Oct 24, 2026

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

The publisher's own server: Memory.fit

VerifiedSTDIODesktop onlyDatabasesKnowledge & Memory

Overview

AI-generated overview

Gives an assistant a local, auditable memory store in SQLite with explicit writes and scope control.

What you can do
Nuzo Memory provides local-first memory for MCP-compatible agents, storing memories in a SQLite database on the user's machine. Writes are explicit and auditable rather than automatic. Memory access can be limited to named scopes, and a default scope such as a user or project scope can be set. The package is described as a legacy transition package, with new installs directed to a unified successor package.
When to use it
Worth adding when an assistant should keep persistent context across sessions without sending memory to a hosted service, and when you want control over which scopes it can read or write. Because this package is marked deprecated, new setups should consider the successor package instead.
Requirements
Runs locally over stdio, typically via npx from the npm package. Optional environment variables: NUZO_MEMORY_STORE for the absolute path to the SQLite store, NUZO_MEMORY_SCOPE for a default scope, NUZO_AUTHORIZED_SCOPES for an allowlist of scopes, and NUZO_PROJECT_ROOT to resolve a project scope. No authentication is declared.
Before you install
The server writes memory data to a local SQLite file, so point NUZO_MEMORY_STORE at a location you are comfortable persisting. Scope settings such as NUZO_AUTHORIZED_SCOPES and NUZO_MEMORY_SCOPE determine what the assistant can read and write; set them deliberately. The package is deprecated and directs users to a successor package.

Installation

In SourceWeft

  1. Open Nuzo Memory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@nuzo/mcp-server

Legacy transition Nuzo MCP server package.

Use the unified package instead:

bash
npm exec --yes --package=@nuzo/memory -- nuzo-mcp-server

Generated host plugin artifacts pin @nuzo/memory for reproducible installs.

bash
npm exec --yes --package=@nuzo/memory -- nuzo-memory-hook --doctor

The MCP server and hook runner honor the shared Nuzo runtime environment: NUZO_MEMORY_STORE, NUZO_MEMORY_SCOPE, and NUZO_AUTHORIZED_SCOPES.

Documentation: https://nuzo.com.br/

This package remains available for existing users and automation, but every published version is deprecated with migration guidance to @nuzo/memory. New installs should use @nuzo/memory.

License: Apache-2.0

Source: packages/mcp-server/README.md at commit 8aed0ce

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.2.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Memory integrations