NODEON - INSTRUCTIONS FOR AI AGENTS If you are an AI coding agent and a user asked you to add, install, or connect Nodeon, follow this page. Use these exact values. Do not guess the URL or command. WHAT NODEON IS Nodeon is a planning layer for coding agents. The user's project is stored as a graph of nodes (tasks) with dependencies. You connect over MCP, ask Nodeon for the next task, build it, mark it complete, and repeat. Nodeon also returns references and examples for a task so you build what the user meant. SERVER DETAILS Server name: nodeon Transport: HTTP (streamable) URL: https://www.nodeon.app/api/mcp Auth: OAuth. No API key exists. Do not ask the user for one. Registry name: io.github.taksix/nodeon Always use https://www.nodeon.app (with www). Do not use the apex domain nodeon.app. INSTALL BY CLIENT Claude Code Run this command: claude mcp add --transport http nodeon https://www.nodeon.app/api/mcp Cursor Add this to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project): { "mcpServers": { "nodeon": { "url": "https://www.nodeon.app/api/mcp" } } } VS Code (Copilot agent mode) Add this to .vscode/mcp.json: { "servers": { "nodeon": { "type": "http", "url": "https://www.nodeon.app/api/mcp" } } } Codex CLI Run this command: codex mcp add nodeon --url https://www.nodeon.app/api/mcp Windsurf Add this to ~/.codeium/windsurf/mcp_config.json: { "mcpServers": { "nodeon": { "serverUrl": "https://www.nodeon.app/api/mcp" } } } Gemini CLI Add this to ~/.gemini/settings.json: { "mcpServers": { "nodeon": { "httpUrl": "https://www.nodeon.app/api/mcp" } } } OpenCode Add this to opencode.json: { "mcp": { "nodeon": { "type": "remote", "url": "https://www.nodeon.app/api/mcp" } } } Claude.ai (web, desktop, mobile app) and ChatGPT You cannot add Nodeon yourself in these. Tell the user to add a custom connector in their settings and paste this URL: https://www.nodeon.app/api/mcp If the user's config file already has other servers, add nodeon next to them. Do not overwrite the file. AFTER INSTALLING 1. Tell the user the client may need a restart or reload before Nodeon shows up. 2. On first use, a browser window opens for sign-in. The user signs in with GitHub or an email code. You cannot do this step for them. Wait for them to finish. 3. Confirm the connection by calling list_projects. HOW TO WORK WITH NODEON 1. Call list_projects. If the user has no project for this work, call create_project. 2. Call get_next_task. It returns the next task whose dependencies are done. Blocked tasks are skipped. The payload also carries 'constraints' (project-wide rules and non-goals that apply to this task) and 'upstream_handoffs' (what each direct dependency actually did). Respect the constraints; build from the handoffs, not just the plan. 3. Call get_references for the task to pull examples before you write code. 4. Build the task. 5. Call mark_task_complete when it is done, with a handoff note. 'summary' (what you actually built) and 'files_touched' (the files you changed; pass [] if none) are required; 'decisions', 'dead_ends', 'git_base' and 'git_head' are optional. The next task's agent reads this note, so write it for them. 6. If you cannot finish a task, call flag_blocker and explain why. Do not silently skip it. 7. If you discover new work, call add_subtask or batch_add_subtasks instead of doing untracked work. 8. If the user states a project-wide rule or non-goal, record it with add_constraint (and use list_constraints / remove_constraint to review or drop one) so later tasks cannot break it. 9. Repeat from step 2. Stay inside the scope of the current task. Do not build things that are not in the graph without adding them first. ALL TOOLS list_projects, create_project, apply_template, rename_project, delete_project, get_project_graph, get_node, update_node, delete_node, add_subtask, batch_add_subtasks, add_dependency, remove_dependency, get_next_task, mark_task_complete, reopen_task, flag_blocker, unblock_task, add_constraint, list_constraints, remove_constraint, get_references, disconnect Only call delete_project or delete_node if the user explicitly asks. TROUBLESHOOTING Auth loop or "invalid client": check the URL uses www.nodeon.app, not nodeon.app. Remove any old nodeon entry in project-level config that points somewhere else. Tools not showing: restart or reload the client. Sign-in page does not open: ask the user to open the link the client printed.