AI agent here means an LLM client (Claude Code, Cursor, etc.) driving the control plane. This is not the install runner in customer clouds.
MCP walkthrough
Connect Claude Code, Cursor, or Amp and run your first calls.
Tools
Read and write tools exposed on the control plane.
Sample queries
Prompts to paste into your client after MCP is connected.
AI and app building
Generate Nuon app config with Claude Code, Gemini, Amp, and skills.
Prerequisites
nuon agents context prints your auth, selected org/app/install, MCP HTTP URL, and how to read timestamps (UTC/Z, convert to local before naming a day or clock time).
Connect
Recommended: register the stdio proxy so the client runsnuon agents mcp --allow-writes. Token and org stay in ~/.nuon. The proxy derives its URL from the configured API hostname (api.<hostname> becomes mcp.<hostname>/mcp) and registers as nuon.
Setup (stdio)
mcp add. Save the JSON as ~/.cursor/mcp.json or project .cursor/mcp.json, then agent mcp enable nuon.
Examples include --allow-writes so mutating tools are available. Your token must have create permission. Omit the flag only if you want a read-only proxy.
You do not need select_org when the org is already in the CLI config (the stdio proxy sends X-Nuon-Org-ID).
Override the server
The proxy derives its upstream URL fromapi_url in your CLI config when the hostname starts with api. (https://api.nuon.co → https://mcp.nuon.co/mcp). To point somewhere else, pass --url; to change the name in the client’s MCP list, pass --name. Put those flags on the command the client runs:
nuon -C /path/to/config agents mcp --allow-writes) carries its own token, org, and api_url. Put -C and --allow-writes on the registered command (Cursor: in args).
Run nuon agents context to confirm which MCP URL resolves before registering.
Related CLI flags
These apply tonuon commands, not MCP tools:
See CLI commands for the full reference.