No user-submitted related servers found.
Scored across 81 tools
Most tools target distinct resource/action combinations, and the descriptions carefully steer usage (e.g. DHCP backend variants, MVC vs legacy firewall rules). A few pairs could still be confused—three DHCP lease listers, DNSBL set/update/reload, and config-section vs list-rules—but the descriptions provide enough guidance to avoid frequent misselection.
All tools share the opn_ prefix and use snake_case verb_noun naming for the most part, with clear CRUD clusters like add/update/delete/toggle. Minor deviations such as opn_mcp_info, opn_firewall_log, opn_pf_states, and opn_configure_mdns_repeater break the strict pattern but remain readable and predictable.
81 tools is far beyond the well-scoped range and falls into the 50+ extreme category. Even though OPNsense is a broad platform, this many tools creates agent selection overhead and could be consolidated around grouped resources or higher-level operations.
Core firewall rules, NAT, aliases, DNS overrides/DNSBL, dnsmasq ranges, HAProxy, and DDNS have reasonable CRUD coverage. However, many subsystems are read-only or incomplete—VPNs have status only, static routes cannot be managed, no ISC/Kea DHCP configuration exists, DNS forward zones lack CRUD, and certificate lifecycle is limited to listing.
