Skip to content
NXS aliensense / documentation
NXS · v1.2.0
Guides

NVIDIA Jetson deployment with an AI agent

nxs mcp offers the setup and check verbs of nxs to an AI agent as tools, over the Model Context Protocol (MCP). The tools use the same words and the same refusals as the verbs. The server runs on your Jetson, which owns the buses, and the agent reaches it over ssh from your workstation, where you chat. At the end, a Claude Code session on your workstation starts the server and lists its tools.

NVIDIA Jetson deployment with an AI agent at a glance
  • Jetson: set up with the NVIDIA Jetson deployment guide and reachable over ssh.
  • Workstation: Claude Code installed, and a dedicated ssh key for the agent, which you make in step 2.
  • Time: 5 minutes.

nxs mcp needs one extra on top of nxs, the MCP library. On your Jetson, add the extra to the nxs install:

Terminal window
orin$ pipx inject aliensense-nxs 'aliensense-nxs[mcp]'

Then print the server’s reference table, which shows what each tool touches on the hardware and when it refuses:

Terminal window
orin$ nxs mcp --doc-table
| Tool | Purpose | Arguments | Hardware effect | Refuses when |
|---|---|---|---|---|
| `probe` | the units that answer, on every bus or a port's | port?, link? | none (reads identity registers) | no ACK rows, or an unknown port, which lists the ports |
| `generate` | the rig as it answers: ports, hubs, links, sensors, units | dry_run? | walks every camera port and bus. With dry_run false it writes hardware.yaml, the report of what answered, and seeds suite.yaml when there is none. It writes a declaration of api 2 or the 1.0 form again in api 3, the earlier file kept beside it. A unit on a bare bus running nothing is named by trying every personality on it | no hub and no camera port, or the wiring file is not writable |
| `status` | the declaration against the rig, or a port's presence and health | port?, link? | none (reads identity and status registers) | hub does not answer |
...

The agent reads this table as its reference before it acts. A printed table proves the extra is installed. Without the extra, nxs mcp says so and exits.

On your workstation, make an ssh key for the agent alone:

Terminal window
host$ ssh-keygen -t ed25519 -N '' -f ~/.ssh/nxs-mcp

Then restrict the key to the server on your Jetson. Whatever command a client asks for, ssh then runs nxs mcp and nothing else, with no forwarding and no terminal. ssh logs in to your Jetson once to add the key there:

Terminal window
host$ printf 'command="$HOME/.local/bin/nxs mcp",no-port-forwarding,no-X11-forwarding,no-agent-forwarding,no-pty %s\n' "$(cat ~/.ssh/nxs-mcp.pub)" | ssh <user>@<jetson> 'cat >> ~/.ssh/authorized_keys'

Then tell Claude Code on your workstation to start the server over that key whenever a session opens:

Terminal window
host$ claude mcp add nxs -- ssh -i ~/.ssh/nxs-mcp <user>@<jetson>

Open a session:

Terminal window
host$ claude

The command= option on the key runs the server by its full path, so the client asks for no command and ssh runs no profile. An agent has no need for a key that could run anything on your Jetson.

In the session, ask the agent what it can do:

What nxs tools do you have?
20 tools: probe, generate, status, identify, samples, caps, on, off, capture, get,
set, suite_get, suite_schema, suite_set, switch, reload, freeze, upload,
host_info, host_modes.

The agent lists the 20 tools the server offers. Listing them starts the server and touches nothing else.