This guide takes you from zero to operating a machine from your AI assistant.
Sign up at nodecommand.app and open the dashboard. You can enroll your first machine right away — the dashboard offers both the one-command install and a direct enrollment command for each machine.
On the machine you want to control, run:
npx node-commandThe CLI prints an eight-character code and a verification URL. Open the URL, sign in, enter the code, and approve. The agent then enrolls the machine, installs itself as a service (machine-wide when elevated, per-user otherwise), and comes online. No inbound ports, no firewall changes.
For hands-off or scripted enrollment, redeem the host ID and one-time enrollment token from the dashboard directly:
npx node-command <host_id> <token>which redeems that enrollment directly — useful for scripted setups. Enrollment tokens are single-use and short-lived.
More detail: agent-installation.md.
Add the Node Command MCP endpoint to your client:
https://mcp.nodecommand.app/mcp
Clients that support MCP OAuth discovery handle sign-in automatically: the client opens your browser once, you approve, and it receives its own short-lived token. Nothing is copied out of the dashboard — if a page ever asks you to paste a token, stop.
If your client takes a static Authorization: Bearer header instead,
create a personal access token in the dashboard and use it there. The
platform never displays or stores tokens in plaintext.
Ready-made client configurations: ../examples/.
Every host-targeting request names an explicit machine — there is no implicit default. List your fleet from the assistant or the dashboard, pick a machine, and describe what you want in natural language.
- Security model:
security.md - Machine management:
clients.md - Troubleshooting:
troubleshooting.md - Architecture:
architecture.md - Source and contracts: nc-agent · nc-protocol