Nauro MCP server
{
"mcpServers": {
"nauro": {
"command": "uvx",
"args": [
"nauro"
]
}
}
}{
"mcpServers": {
"nauro": {
"command": "uvx",
"args": [
"nauro"
]
}
}
}{
"mcpServers": {
"nauro": {
"command": "uvx",
"args": [
"nauro"
]
}
}
}{
"servers": {
"nauro": {
"command": "uvx",
"args": [
"nauro"
]
}
}
}{
"mcpServers": {
"nauro": {
"command": "uvx",
"args": [
"nauro"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall uvx nauroversion 1.19.0
What it does
Nauro records project decisions, their reasoning, and rejected alternatives, then makes that context available to AI agents in subsequent sessions. It's designed for teams using agents to do longer-lived work across multiple sessions while keeping humans in control of directional choices.
- Retrieve past project decisions and their reasoning when starting a new agent session to maintain consistency in how the agent approaches similar problems.
- Record a decision your team approves (such as a chosen architecture or rejected alternative) so future agent sessions understand why that choice was made.
- Check whether a proposed change conflicts with prior decisions by querying related past decisions before committing to a new direction.
Tools this server exposes
| Tool | Does |
|---|---|
| nauro-check-decision | Retrieves prior decisions and reasoning related to a proposed change or question. |
| nauro-record-decision | Records a new decision with its reasoning and rejected alternatives after human approval. |
| nauro-status | Checks whether the Nauro connection and project record are working correctly. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.