HN

hmldns/nautex

Developer tools
84 stars 0 forks 품질 55 트렌드 55

This is an MCP server that integrates PRD and TRD building tool Nautex AI with the Coding Agents.

개요

This is an MCP server that integrates PRD and TRD building tool Nautex AI with the Coding Agents.

README

This is an MCP server that integrates PRD and TRD building tool Nautex AI with the Coding Agents.

Supported agents:

  • Claude Code
  • Cursor
  • Codex
  • OpenCode
  • Gemini CLI

Motivation

Since LLM Coding Agents do not attend team meetings, there is the challenge of conveying complete and detailed product and technical requirements to them.

Nautex AI tool-chain manages step by step guiding of Coding Agents so they implement specification using small, relevant and testable steps.

Core principles are:

  1. start from foundational parts, de-risk them, then build up;
  2. do not overwhelm Coding Agents by large problem at once;
  3. plan project files map and link them to requirements and to tasks: Coding Agents don’t get lost, you know how to navigate brand new code base;
  4. manage developer attention for verification and validation in right moment for review.

How It Works

Nautex AI acts as an Architect, Technical Product Manager, and Project Manager for coding agents, speeding up AI-assisted development by communicating requirements effectively. This MCP server pulls guidance instructions from Nautex AI; tasks contain to-do items, references to the affected files, and requirements that are automatically synced for the Coding Agent’s availability.

By Ivan Makarov

Setup

Quick Setup (one command)

The fastest way to set up is via the web app onboarding flow, which generates a single command you copy and run in your project root:

uvx nautex setup --token  --project  --plan  --agent 

Parameters:

Flag Description
--token, -t API token (create at nautex.ai)
--project, -p Project ID
--plan, -l Implementation plan ID
--agent, -a Agent type: claude, cursor, codex, opencode, gemini
--yes, -y Skip confirmation prompts

This validates your token, project, and plan, then writes all configuration to your project root:

  • .nautex/config.json — project config
  • .nautex/.env — API token (git-ignored)
  • MCP config — agent-specific (see below)
  • Agent rules — merged into existing rule files without overriding your content

Interactive Setup (Terminal UI)

Alternatively, run the interactive terminal UI:

uvx nautex setup

Follow the on-screen prompts to select your project, plan, and agent.

What Gets Written Per Agent

All configuration is scoped per-project in your project root.

Start Coding

Once setup is complete, launch your coding agent and tell it:

Check nautex status

After confirming the connection works:

Pull nautex rules and proceed to the next scope

Proceed with the plan by reviewing progress and supporting the Agent with validation feedback and inputs.

Prerequisites

Before running setup, prepare your project in the Nautex web app:

  1. Sign up and create an API token
  2. Create PRD and TRD documents (chat with the bot to capture requirements)
  3. Create a files map of the project
  4. Create an implementation plan

The web app onboarding flow will generate the setup command with all IDs pre-filled.

Projects built with nautex

Best practice from the community

View this README on GitHub

설치

uvx nautex setup --token <TOKEN> --project <PROJECT_ID> --plan <PLAN_ID> --agent <AGENT>