Open-PR-DIGI-MCP-Server-for-Claude-AI: Skill for Claude Code

Onboard a PR digi node

Drive the operator through adding a node to pr-digi-mcp. Reference: docs/onboarding-nodes.md. Never put passwords in nodes.yaml, in the repo, or in the chat transcript — credentials go in the OS keyring (preferred) or a gitignored credentials.yaml.

1. Gather the node's details

Ask the operator (one question at a time if unclear):

• Callsign (e.g. N0CALL-7) and node software → type: xnet ((X)Net / PC-Flexnet) · linbpq · bpq (Windows) · xnet_chained (AX.25-only).
• Access model (see docs/onboarding-nodes.md §1):
  • Direct telnet → telnet_host, telnet_port.
  • Via SSH jump → also ssh_host (must be an alias in ~/.ssh/config); telnet_host is the address as seen from the jump host.
  • Chained AX.25 (the only way to reach a PC/Flexnet node — it has no telnet) → transit_via = the first-hop node, which may be an (X)Net OR a BPQ/LinBPQ node (any AX.25-capable node the MCP can telnet into; or another chained node for multi-hop) + connect_command (C <CALLSIGN>). No user. Note: PC/Flexnet's commands differ from (X)Net — it's driven via xnet_sys_command, and its sysop keyword is SY — set sys_command: SY on the node (default is SYS).
• Login: a user (login callsign/name) — or login_required: false for an open node with no login prompt.
• sys_required: true if the node needs SYS/PASSWORD for write tools.

2. Locate / create the config

• Config lives at ~/.config/pr-digi-mcp/nodes.yaml. If it doesn't exist, create it from config/nodes.example.yaml (keep only a nodes: mapping).
• For a chained node, confirm transit_via already exists in the file (or is being added in the same pass) — a dangling chain fails to load.

3. Add the node block

Show the exact YAML you will add and get the operator's OK before writing. Shapes:

  N0CALL-7:   {type: xnet, telnet_host: 192.0.2.10, telnet_port: 23, user: me, sys_required: true}
  N0CALL-14:  {type: xnet, ssh_host: my-gw, telnet_host: 44.0.0.2, telnet_port: 23, user: me, sys_required: true}
  N0CALL-12:  {type: xnet_chained, transit_via: N0CALL-14, connect_command: "C N0CALL-12", sys_required: true}
  N0CALL-9:   {type: xnet, telnet_host: 192.0.2.30, telnet_port: 23, login_required: false, sys_required: false}