iflow-mcp_hmldns-nautex 0.3.3

Nautex AI MCP server that works as Product and Project manager for coding agents

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

Supported agents:

• Claude Code
• Codex
• Cursor
• 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

⬇️⬇️⬇️ 📚 Check Presentation ⬇️⬇️⬇️

💡 Usage Flow Presentation (unfold me)

Requirements Specifications

The chatbot conducts a briefing session with you, gathering questions and ideas until complete. It then generates comprehensive product and technical specifications.

(Example: A project I initiated to explore WebRTC.)

Product requirements:

Technical requirements:

Specification Refinement

You fill in details, clarify the specification, and resolve any TODOs flagged by the chatbot during the interview.

Codebase Map and Project Files

You'll occasionally need to review the code, so it's best to know in advance where to look and how everything is organized. This prevents the AI from making decisions—allowing it to focus on writing higher-quality code with greater attention to the task.

The image displays a file map generated by Nautex AI, with files linked to specific requirements and sections.

Agent Tasks

With the code location clarified, tasks are planned: Coding, Testing, and Review.

Reviews are scheduled early to demonstrate progress and verify alignment with goals.

The plan is structured in small, self-contained layers, building your project incrementally like floors in a skyscraper.

Integration

Next, configure the MCP server for Cursor integration: connect to the Nautex cloud platform for tasks, select the project, and choose the plan.

Set the MCP server parameters and provide usage rules for Cursor. Use mouse clicks for automation—the terminal UI functions like a web page.

This utility is available on GitHub.

Once all indicators are green, initiate plan execution.

Coding with Coding Agents

In agent mode, instruct: "pull nautex rules, and proceed with the next scope."

At this stage, your specifications are synchronized in the .nautex directory and accessible to the Coding Agent. The MCP server continuously monitors their relevance.

That's it. You then review and accept substantial code segments that fully align with your expectations and requirements.

Setup

Via Terminal UI

1. Go to the new project folder and run in the terminal:

uvx nautex setup

How to Install uv

On macOS and linux:

curl -LsSf https://astral.sh/uv/install.sh | sh

On Windows

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Check the latest instruction from UV repo for details and updates

You should see the terminal user interface

2. Follow the guidelines via UI

• go Nautex.ai to sign up and create API token
• In the web app, create PRD and TRD documents:
  • Chat with the bot for capturing requirements.
  • After initial documents generation Create files map of the project inside the map.
  • Then, after reviewing resulted map create implementation plan.
  • You can follow Connect Coding Agent onboarding flow or setup via TUI. Button will disappear on first MCP request
  • Go back to the CLI UI
• Select project
• Select implementation plan
• Select agent type
• Ensure you've got right MCP config: manually or via TUI (it will merge with any existing config)

For cursor

• in .cursor/mcp.json,

{
  "mcpServers": {
    "nautex": {
      "command": "uvx",
      "args": [
        "nautex",
        "mcp"
      ]
    }
  }
}

Note: At config update Cursor asks via popup either you want to enable new MCP, answer yes. In any case in File -> Preferences -> Cursor Preferences -> Tools & Integrations nautex MCP should be enabled and green.

• Rules are in .cursor/rules/ folder via TUI command.

For Claude Code

TUI setup launches this command to add Nautex MCP:

claude mcp add nautex -s local -- uvx nautex mcp

• Rules are in ./CLAUDE.md after set via TUI.
• Verify integration: run claude mcp list and ensure an entry like nautex: uvx nautex mcp - ✓ Connected is present.

For Codex

Codex uses a file-based MCP config at ~/.codex/config.toml. Nautex will merge/update this file and create a backup config.toml.bak before the first overwrite if needed.

• Rules live under .nautex/AGENTS.md, with a managed reference section in the root AGENTS.md.
• Verify integration in Codex: open the MCP command UI (e.g., use the /mcp command) and confirm nautex is listed/enabled. Alternatively, inspect ~/.codex/config.toml for a nautex entry pointing to uvx nautex mcp.

For OpenCode

OpenCode uses a per-project config opencode.json in the repository root. Nautex writes/updates this file, preserving unrelated fields and backing up unparsable files once to opencode.json.bak.

Minimal required structure written by Nautex:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nautex": {
      "type": "local",
      "command": ["uvx", "nautex", "mcp"],
      "enabled": true
    }
  }
}

• Rules live under .nautex/AGENTS.md, with a managed reference section in the root AGENTS.md.
• Verify integration: from OpenCode, invoke the Nautex MCP tool and run status (e.g., “nautex: status”). You should see the Nautex server respond. Optionally inspect opencode.json as shown above.

3. (Optional) Check MCP server response uvx nautex mcp test next_scope
4. Check MCP configuration works and Coding Agent sees the tools:

Check nautex status

5. Tell Coding Agent:

Pull nautex rules and proceed to the next scope

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

Projects built with nautex

• Collaborative Pixel Canvas - repo

Best practice from the community