Prerequisites
- Nuon CLI installed and authenticated (
nuon auth login,nuon orgs select) - An LLM client that supports MCP (Cursor, Claude Code, etc.)
Steps
1
Register the MCP server
Add the stdio proxy. Token and org stay in Claude Code: add command above, or save the JSON as Examples include
~/.nuon.Each client has its own config file, JSON key, and (sometimes) an add command. Check that client’s MCP docs rather than assuming a shared schema. The process to spawn is nuon with arguments agents, mcp, and --allow-writes..mcp.json in the project.Amp: add command above, or save the JSON under amp.mcpServers in ~/.config/amp/settings.json (user) or .amp/settings.json (workspace).Cursor has no mcp add. Save the JSON as ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project), then:--allow-writes so mutating tools are available. That flag only lists write tools; the identity still needs Admin (org_admin), not Read-only.The proxy derives its URL from the configured API hostname (api.<hostname> becomes mcp.<hostname>/mcp). Pass --url when the MCP URL does not follow from the API URL, for example a self-hosted or Nuon BYOC control plane, or any deployment where the hostnames differ. Use --name to rename it in the client’s MCP list. Full examples: Connect and Overriding the MCP URL.nuon agents help prints all of this against your own config.2
Verify context
nuon auth login and nuon orgs select.3
Ask a first question
In the LLM client, paste:The client should call
whoami and list_installs. You do not need select_org when using the stdio proxy (org is already in X-Nuon-Org-ID).More prompts: Sample queries.