Multi-Node Management

Guide the user through managing multiple SSH targets from a single MCP server instance, including node inventory, cross-node operations, and fleet-wide monitoring.

Trigger

• User asks about managing multiple machines, servers, or Pis
• User mentions "nodes", "fleet", "inventory", or "multi-node"
• User wants to run commands on a specific named host
• User asks about Ansible inventory or Tailscale peer discovery
• User wants to compare status across multiple machines

Required Inputs

• SSH connectivity to at least one node (validated via homelab_sshTest)
• For multi-node: HOMELAB_NODES env var configured with named node entries
• For Ansible discovery: Ansible inventory file accessible from the primary Pi
• For Tailscale discovery: Tailscale installed on the primary Pi