English Français العربية

Nuzo Memory

Official registry Archived Data and databases

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

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @nuzo/memory-mcp
Claude Code 
claude mcp add nuzo-memory -e 'NUZO_MEMORY_STORE=<NUZO_MEMORY_STORE>' -e 'NUZO_MEMORY_SCOPE=<NUZO_MEMORY_SCOPE>' -e 'NUZO_AUTHORIZED_SCOPES=<NUZO_AUTHORIZED_SCOPES>' -e 'NUZO_PROJECT_ROOT=<NUZO_PROJECT_ROOT>' -- npx -y @nuzo/memory-mcp@1.2.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "nuzo-memory": {
            "command": "npx",
            "args": [
                "-y",
                "@nuzo/memory-mcp@1.2.0"
            ],
            "env": {
                "NUZO_MEMORY_STORE": "<NUZO_MEMORY_STORE>",
                "NUZO_MEMORY_SCOPE": "<NUZO_MEMORY_SCOPE>",
                "NUZO_AUTHORIZED_SCOPES": "<NUZO_AUTHORIZED_SCOPES>",
                "NUZO_PROJECT_ROOT": "<NUZO_PROJECT_ROOT>"
            }
        }
    }
}

Environment variables

  • NUZO_MEMORY_STORE Optional absolute path to the local SQLite memory store.
  • NUZO_MEMORY_SCOPE Optional default Nuzo memory scope, such as user:default or project:auto.
  • NUZO_AUTHORIZED_SCOPES Optional comma-separated allowlist of memory scopes available to this MCP process.
  • NUZO_PROJECT_ROOT Optional project root used to resolve project:auto scope.

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Nuzo
  2. Quick Start
  3. The Memory Loop
  4. Proof, Not Promises
  5. When Nuzo Fits
  6. Packages
  7. Project Status
  8. License

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

ClaimRepository contract
Local by defaultSQLite and SQLite FTS are canonical; telemetry and network embeddings are off by default.
Auditable lifecycleMCP tools cover history and audit alongside update, archive, delete, export, and import.
Explicit inferred writesCapture suggestions report memory_writes: false; confirmation is a separate tool.
Read-only automatic recallHost hooks open existing stores read-only and fail open without writing application state.
Tested releasesNode 22, Node 24, docs, CodeQL, package validation, and host smoke gates are required before merge.

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

When Nuzo Fits

Choose Nuzo when individual memories need scopes, provenance, review state, relations, audit history, bounded recall, or reuse across supported hosts.

Keep shared repository instructions in AGENTS.md. Use a short MEMORY.md when manual curation is enough. Nuzo is not a cloud sync service, team knowledge base, autonomous profile builder, or hosted dashboard.

Read the full decision guide and architecture overview.

Packages

PackageIntended use
@nuzo/memoryRecommended install: CLI, MCP server, and host hook runtime.
@nuzo/memory-coreLibrary-level integrations.

Source workspace packages remain private. Public packages are generated and validated through the documented release process.

Project Status

The 1.2.0 release closes the planned roadmap. The repository is retained as an auditable reference and is not accepting new feature work. Existing users should pin an exact version and evaluate a maintained alternative or fork for future runtime and dependency changes. Never publish real memory data, credentials, or exports when discussing or forking Nuzo.

License

Nuzo is licensed under the Apache License 2.0.

Frequently asked questions

What is Nuzo Memory?

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

How do I install Nuzo Memory?

It runs on your machine. In Claude Code: claude mcp add nuzo-memory -e 'NUZO_MEMORY_STORE=<NUZO_MEMORY_STORE>' -e 'NUZO_MEMORY_SCOPE=<NUZO_MEMORY_SCOPE>' -e 'NUZO_AUTHORIZED_SCOPES=<NUZO_AUTHORIZED_SCOPES>' -e 'NUZO_PROJECT_ROOT=<NUZO_PROJECT_ROOT>' -- npx -y @nuzo/memory-mcp@1.2.0. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Nuzo Memory need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Nuzo Memory open source?

Yes. Its code is on GitHub under the Apache-2.0 license.

Who maintains Nuzo Memory?

It is published by fabionfsc. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.