Nahuali MCP server

Nahuali

Memory an agent can inspect before it trusts.

From an empty memory to evidence-backed recall: Nahuali shows what is ready to use and pauses what still needs review.

Memory retrieval usually begins with what context looks relevant? Nahuali also exposes four separate questions:

• What observation supports this memory?
• What conflicts with it or makes it stale?
• Do the current recorded-history checks pass?
• Do the available evidence and health checks support using this result?

The result is a local-first memory engine with deterministic trust verdicts, tamper-evident recorded history, and portable evidence. Its core does not need a model, account, API key, hosted service, or Docker.

A 60-second tour

Install the macOS or Linux binary. The installer requires the matching SHA-256 asset; the pinned path below can additionally require its Sigstore bundle.

curl -fsSLo /tmp/nahuali-install.sh \
  https://raw.githubusercontent.com/Arakiss/nahuali/main/scripts/install.sh
sh /tmp/nahuali-install.sh
export PATH="$HOME/.nahuali/bin:$PATH"

Run nahuali --version in a terminal to see the real axolotl spritesheet come alive beside the build identity. When the command is captured or redirected, it emits the stable nahuali line expected by agents, install checks, and benchmark tooling.

Record an observation, derive a claim from it, and require evidence at recall:

nahuali remember "Lena owns the release notes" --mention Lena --tag product
nahuali claim Lena owns "release notes" --source-last --confidence 0.92
nahuali recall "Who owns the release notes?" --authority --require-evidence
nahuali explore

nahuali explore is not just a record browser. It keeps three independent questions visible:

Press / to search every displayed memory-item field, Tab to filter by memory kind, and j/k to inspect the evidence behind a result. The axolotl watches over the memory and changes with its status. Rebuild the GIF above from real Ghostty windows on macOS with scripts/render-readme-tui-gif.sh; the canonical README asset is never replaced by the lower-fidelity text fallback.

Run nahuali demo for a narrated, non-mutating explanation of how Nahuali detects a specific in-place record change and keeps unsupported memory from driving action. The demo states which changes require an externally retained reference rather than relying on the live store alone.

Where Nahuali fits

Choose Nahuali when an agent needs local or operator-controlled memory and the decision to use a result must carry evidence, health signals, and explicit integrity limits. It is especially useful as a reliability layer around consequential memory rather than as a replacement for every retrieval system.

Shortened. The full README is on GitHub.