Nautex

by hmldns

Nautex AI MCP 服务器,作为编码代理的产品和项目管理工具,加快 AI 辅助开发,通过 CLI 界面配置的 Nautex.ai API 令牌实现需求沟通。

Developer toolsstdioCommunity

Repository-wide counts · Cached 2026-03-08

Overview

The Nautex MCP server is a publicly available project. Review the upstream repository for installation instructions, supported tools, compatibility, permissions, and current maintenance status.

Configuration

Configuration, transport, authentication, and runtime requirements vary by project. Open the repository before connecting and use the smallest set of credentials and permissions required.

Open the Nautex repository to read the latest documentation.

KEEP EXPLORING

Compare source, connection, and authentication details before choosing an implementation.

View the complete category

模型上下文协议服务器

modelcontextprotocol

Community

一组用于模型上下文协议(MCP)的参考实现,展示了对大型语言模型(LLM)工具和数据源的安全且受控的访问方式。

Context7 Platform - Up-to-date Code Docs For Any Prompt

upstash

Community

Context7 MCP server providing up-to-date, version-specific documentation and code examples for libraries, enabling coding agents to fetch accurate docs and code snippets. Requires an API key for higher rate limits, passed via CONTEXT7_API_KEY header.

Playwright MCP

Microsoft Corporation

Community

A Model Context Protocol (MCP) server that provides browser automation capabilities using Playwright. Enables LLMs to interact with web pages through structured accessibility snapshots, bypassing the need for screenshots or visually-tuned models.

AIHawk

feder-cr

Community

AIHawk is an anti detect browser and web browsing agent, open source, with an MCP server for coding agents: undetected, no captchas, no blocks. It requires an OpenRouter API key for the standalone web UI mode, which can be provided via the --openrouter-key flag or the OPENROUTER_API_KEY environment variable or a .env file in the running directory.

FROM THE SOURCE

Repository README

Build-time snapshot · Retrieved 2026-10-05

View original

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
  • Grok Build

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, grok
--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
Grok Build
  • MCP config: .grok/config.toml (project-local, backup created as config.toml.bak before first write; startup_timeout_sec = 20)
  • Rules: managed section added to AGENTS.md
  • Verify: run grok mcp list / grok mcp doctor nautex, or open /mcps in the Grok TUI

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