MCP 服务器

nuzo-memory

Local-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.

README

<p align="center"> <strong>Local-first, auditable memory for AI agents.</strong><br> Durable context for Codex, Claude Code, and MCP-compatible hosts—without turning memory into hidden state. </p>

<p align="center"> <a href="https://nuzo.com.br/getting-started/">Install</a> · <a href="https://nuzo.com.br/getting-started/sixty-second-demo/">60-second demo</a> · <a href="https://nuzo.com.br/product/why-nuzo/">Why Nuzo?</a> · <a href="https://nuzo.com.br/operations/privacy-and-security/">Security</a> · <a href="https://nuzo.com.br/spec/tools/">MCP contract</a> </p>

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.

<details> <summary>Non-interactive setup and upgrade commands</summary>

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

</details>

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.