Nuzo Memory

io.github.fabionfsc

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

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.fabionfsc-nuzo-memory": {4      "command": "npx",5      "args": [6        "-y",7        "@nuzo/[email protected]"8      ],9      "env": {10        "NUZO_MEMORY_STORE": "<value>",11        "NUZO_MEMORY_SCOPE": "<value>",12        "NUZO_AUTHORIZED_SCOPES": "<value>",13        "NUZO_PROJECT_ROOT": "<value>"14      }15    }16  }17}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @nuzo/[email protected]

Credentials from the publisher

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.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1NUZO_MEMORY_STORE=<value> NUZO_MEMORY_SCOPE=<value> NUZO_AUTHORIZED_SCOPES=<value> NUZO_PROJECT_ROOT=<value> claude mcp add io.github.fabionfsc-nuzo-memory -- npx -y @nuzo/memory-mcp@1.2.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.fabionfsc-nuzo-memory": {4      "command": "npx",5      "args": [6        "-y",7        "@nuzo/[email protected]"8      ],9      "env": {10        "NUZO_MEMORY_STORE": "<value>",11        "NUZO_MEMORY_SCOPE": "<value>",12        "NUZO_AUTHORIZED_SCOPES": "<value>",13        "NUZO_PROJECT_ROOT": "<value>"14      }15    }16  }17}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.2.0
API key: NUZO_MEMORY_STORE, NUZO_MEMORY_SCOPE, NUZO_AUTHORIZED_SCOPES, NUZO_PROJECT_ROOT
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Nuzo Memory?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Nuzo Memory need an API key?

The publisher lists these environment variables: NUZO_MEMORY_STORE, NUZO_MEMORY_SCOPE, NUZO_AUTHORIZED_SCOPES, NUZO_PROJECT_ROOT.

What transport does Nuzo Memory use?

Nuzo Memory runs locally over stdio.

When was Nuzo Memory last checked?

Last checked 2026-10-28. Local-first, auditable memory for MCP-compatible AI agents with explicit writes and SQLite storage.

From the publisher

Documentation

[!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/[email protected]
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.

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

Claim	Repository contract
Local by default	SQLite and SQLite FTS are canonical; telemetry and network embeddings are off by default.
Auditable lifecycle	MCP tools cover history and audit alongside update, archive, delete, export, and import.
Explicit inferred writes	Capture suggestions report `memory_writes: false`; confirmation is a separate tool.
Read-only automatic recall	Host hooks open existing stores read-only and fail open without writing application state.
Tested releases	Node 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

Package	Intended use
`@nuzo/memory`	Recommended install: CLI, MCP server, and host hook runtime.
`@nuzo/memory-core`	Library-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.

Nuzo Memory

io.github.fabionfsc

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

Databases Knowledge Memory

Add to Cursor Add to VS Code Run on PlugMCP

GitHub npm Website

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.fabionfsc-nuzo-memory": {4      "command": "npx",5      "args": [6        "-y",7        "@nuzo/[email protected]"8      ],9      "env": {10        "NUZO_MEMORY_STORE": "<value>",11        "NUZO_MEMORY_SCOPE": "<value>",12        "NUZO_AUTHORIZED_SCOPES": "<value>",13        "NUZO_PROJECT_ROOT": "<value>"14      }15    }16  }17}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y @nuzo/[email protected]

Credentials from the publisher

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.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1NUZO_MEMORY_STORE=<value> NUZO_MEMORY_SCOPE=<value> NUZO_AUTHORIZED_SCOPES=<value> NUZO_PROJECT_ROOT=<value> claude mcp add io.github.fabionfsc-nuzo-memory -- npx -y @nuzo/memory-mcp@1.2.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.fabionfsc-nuzo-memory": {4      "command": "npx",5      "args": [6        "-y",7        "@nuzo/[email protected]"8      ],9      "env": {10        "NUZO_MEMORY_STORE": "<value>",11        "NUZO_MEMORY_SCOPE": "<value>",12        "NUZO_AUTHORIZED_SCOPES": "<value>",13        "NUZO_PROJECT_ROOT": "<value>"14      }15    }16  }17}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.2.0
API key: NUZO_MEMORY_STORE, NUZO_MEMORY_SCOPE, NUZO_AUTHORIZED_SCOPES, NUZO_PROJECT_ROOT
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Nuzo Memory?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Nuzo Memory need an API key?

The publisher lists these environment variables: NUZO_MEMORY_STORE, NUZO_MEMORY_SCOPE, NUZO_AUTHORIZED_SCOPES, NUZO_PROJECT_ROOT.

What transport does Nuzo Memory use?

Nuzo Memory runs locally over stdio.

When was Nuzo Memory last checked?

Last checked 2026-10-28. Local-first, auditable memory for MCP-compatible AI agents with explicit writes and SQLite storage.

From the publisher

Documentation

[!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/[email protected]
nuzo setup

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

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

The Memory Loop

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

Proof, Not Promises

Claim	Repository contract
Local by default	SQLite and SQLite FTS are canonical; telemetry and network embeddings are off by default.
Auditable lifecycle	MCP tools cover history and audit alongside update, archive, delete, export, and import.
Explicit inferred writes	Capture suggestions report `memory_writes: false`; confirmation is a separate tool.
Read-only automatic recall	Host hooks open existing stores read-only and fail open without writing application state.
Tested releases	Node 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.

Read the full decision guide and architecture overview.

Packages

Package	Intended use
`@nuzo/memory`	Recommended install: CLI, MCP server, and host hook runtime.
`@nuzo/memory-core`	Library-level integrations.

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

Project Status

License

Nuzo is licensed under the Apache License 2.0.