Skip to main content
Copy a prompt into your LLM client after MCP is connected. The client should pick tools from the catalog; you do not need to name them. Write prompts need --allow-writes on the stdio proxy and Admin (org_admin) on the identity. Replace names like acme-prod with your own install, app, or workflow IDs.

Review org status

Manage workflows

Write. The agent should present each pending approval’s next_actions. Review loads every get_approval_plan_diff page, following continue_review, before it replies. It waits for confirmation before approve_step, reject_step, or approve_all. approve_all appears only when the workflow is still set to prompt. On the await install stack step, it shows stack_setup and keeps watching. Pass cursor from each watch_workflow response into the next call.
Write.
Write.

Deploy app versions to installs

Variants: In the preview run for PR <number>, what changed? and Show progress for branch run <run_id>, including updated installs and what is left.
Write. Same as nuon apps branches preview. Ask before apply.HTTP MCP cannot read the local workspace. For local toml, run nuon apps sync --branch <branch> --output agent first, then pass the resulting app_config_id.

Debug installs

Write. Call the returned next_action. Each watch_workflow returns when a step starts or finishes. After every result, show step_progress, then call watch again with cursor. A row of watch calls with no progress between them is wrong.
Write. The run_runbook description requires a prompt first: load the install-pinned runbook, confirm inputs, show the step checklist with every step enabled, and let the user turn steps off before triggering. Then ask whether the user wants to watch. Call the returned next_action only if they do. Each watch_workflow returns when a step starts or finishes. After every result, show step_progress, then call watch again with cursor. A row of watch calls with no progress between them is wrong.

Get help writing app config

Read. get_app_config_schema returns the file schema. When validating for this MCP server, use the Nuon CLI binary that started it, such as nuon-dev apps validate when the server is nuon-dev, and the same -C value if that server was started with -C. Do that only for work done for the MCP server.
More on these: Skills.

Update installs

Write. Deprovision requires confirm=true. plan_only does not. After the write, ask whether the user wants to watch. Call the returned next_action only if they do.
Write.