Skip to main content

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

Project description

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

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: howitworks_specifications

Technical requirements: howitworks_diagram.png

Specification Refinement

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

howitworks_refinement

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.

howitworks_filemap

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.

howitworks_tasks

Integration

Configure the MCP server for your coding agent: connect to the Nautex cloud platform, select the project, and choose the implementation plan. The setup command writes all configuration to your project root.

howitworks_integration

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.

howitworks_coding

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 <TOKEN> --project <PROJECT_ID> --plan <PLAN_ID> --agent <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

Setup Screenshot

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

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 instructions from the UV repo for details and updates.

What Gets Written Per Agent

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

Claude Code
  • MCP: registered via claude mcp add nautex -s local -- uvx nautex mcp
  • Rules: managed section added to CLAUDE.md
  • Verify: run claude mcp list and check for nautex: uvx nautex mcp
Cursor
  • MCP config: .cursor/mcp.json
  • Rules: .cursor/rules/nautex_workflow.mdc

Note: After setup, Cursor may ask via popup whether to enable the new MCP — answer yes. In any case, go to File -> Preferences -> Cursor Settings -> Tools & Integrations and make sure the Nautex MCP toggle is enabled (green).

Codex
  • MCP config: .codex/config.toml (project-local, backup created as config.toml.bak before first write)
  • Rules: managed section added to AGENTS.md
  • Verify: use the /mcp command inside Codex to confirm nautex is listed
OpenCode
  • MCP config: opencode.json (project root, preserves unrelated fields, backup as opencode.json.bak if unparsable)
  • Rules: managed section added to AGENTS.md
  • Verify: invoke the Nautex MCP tool from OpenCode and run status
Gemini CLI
  • MCP config: .gemini/settings.json
  • Rules: managed section added to GEMINI.md

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

drawing

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

nautex-0.4.0.tar.gz (93.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

nautex-0.4.0-py3-none-any.whl (113.2 kB view details)

Uploaded Python 3

File details

Details for the file nautex-0.4.0.tar.gz.

File metadata

  • Download URL: nautex-0.4.0.tar.gz
  • Upload date:
  • Size: 93.3 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.3

File hashes

Hashes for nautex-0.4.0.tar.gz
Algorithm Hash digest
SHA256 800acf78f9f66be89e1dfd88bbb16ceb24c14f72c30324492ad8ccde8fc3bce4
MD5 05231a78b8e5711e6ddc2f55719f62a3
BLAKE2b-256 f3af794d82881258f663c3e4e8a44c9db84c551128cf5ef8e24401f49834d8c2

See more details on using hashes here.

File details

Details for the file nautex-0.4.0-py3-none-any.whl.

File metadata

  • Download URL: nautex-0.4.0-py3-none-any.whl
  • Upload date:
  • Size: 113.2 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.2.0 CPython/3.14.3

File hashes

Hashes for nautex-0.4.0-py3-none-any.whl
Algorithm Hash digest
SHA256 78a0d958ff835861e8efb0f015c5d1ff78a45265870c11282728d386c1e67e86
MD5 245e5f8c06b546030f0aa5aeed478cc2
BLAKE2b-256 6a929c001cacb42b590b15c0e4640e026b326761a75af6fdf38809f6302478c9

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page