Skip to main content
Glama
fabionfsc

nuzo-memory

by fabionfsc

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.

Quick Start

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

npm install --global @nuzo/memory@1.1.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.

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

Related MCP server: tartarus-mcp

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.

Contributing

See CONTRIBUTING.md, SECURITY.md, and the public roadmap. Never attach real memory data, credentials, or exports to an issue.

License

Nuzo is licensed under the Apache License 2.0.

A
license - permissive license
-
quality - not tested
B
maintenance

Maintenance

Maintainers
<1hResponse time
1dRelease cycle
18Releases (12mo)
Commit activity
Issues opened vs closed

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fabionfsc/nuzo-memory'

If you have feedback or need assistance with the MCP directory API, please join our Discord server