Nauro

What the Nauro MCP server does

The Nauro MCP server keeps a project decision record for AI-assisted software work. Approved decisions can include the reasoning behind them and alternatives that were rejected. Later agent sessions can retrieve that context before proposing or implementing changes.

Nauro is intended for longer-lived work where multiple sessions, agents, or handoffs need to preserve project direction. It is less necessary for a small repository that already stays oriented through a dependable AGENTS.md or CLAUDE.md file.

How it works

The record is stored locally as plain Markdown when Nauro is used locally. Agents can ask whether an earlier decision relates to a proposed change; for example, nauro check-decision retrieves related reasoning without running an agent or changing the project record.

Retrieval is advisory rather than authoritative enforcement. Nauro does not automatically approve new direction. New or revised decisions require explicit human approval before they become part of the durable record. The system is designed to bring approved reasoning into later sessions rather than replace review.

The project can be adopted for agent workflows with nauro adopt --with-skills --with-subagents. After restarting an agent, the adoption workflow can be invoked with /nauro-adopt in Claude Code, $nauro-adopt in Codex, or @nauro-adopt in Cursor. Existing AGENTS.md content is preserved unless nauro sync is run; its # Manual section survives replacement.

Setup and configuration

Install the CLI with uv tool install nauro, or use pipx install nauro with Python 3.10 or newer. The macOS desktop app can install the CLI, connect agents, set up a project, and provide a read-only viewer for the project record.

For a repository, run the adoption command from its root, then restart the relevant agent. nauro status reports configuration and executable availability. Cursor requires a durable absolute Nauro executable for global MCP wiring; its migration instructions should be followed before changing legacy wiring. Claude Code and Codex retain their existing fallback behavior.

Local use requires no account. Cloud synchronization is optional, and the project states that Nauro sends no product analytics.

Tools and capabilities

The Nauro MCP server supports these documented workflows and capabilities:

• Retrieve related prior decisions with nauro check-decision.
• Adopt a repository with agent skills and subagents using nauro adopt.
• Inspect setup and executable status with nauro status.
• Initialize a project or bundled demo with nauro init --demo.
• Review the project record through the macOS app's read-only viewer.
• Study supported findings from Claude and Codex logs with the bundled nauro-investigator.

The demo shows retrieval of the reasoning behind a fictional budgeting decision. It does not execute an agent or modify decisions.

Limitations and notes

Nauro's retrieval can inform an agent but does not force compliance or make decisions automatically. The record depends on explicit approval for new or revised entries. Cloud sync and hosted MCP are versioned separately from the local stdio MCP contract, store format, CLI, and curated nauro-core API.

Cursor has an additional executable-path requirement for global MCP wiring. The investigator is bounded to supported findings from Claude and Codex logs, with a research notebook available for later runs. The project is marked stable in the 1.x series and is licensed under Apache 2.0.