Related Servers

The set contains extensive duplication between curated tools and generated tools, e.g. unifi_net_list_networks vs unifi_gen_getnetworksoverviewpage, unifi_net_get_voucher vs unifi_gen_getvoucher, and multiple voucher/firewall/traffic-list variants. Some tools are also near-overlapping actions, such as unifi_net_device_action, unifi_net_reboot_device, and unifi_gen_executeadopteddeviceaction. An agent can often distinguish by prefix, but many boundaries are confusing.

Names mix three families: unifi_net_* snake_case, unifi_sm_* snake_case, and unifi_gen_* concatenated generated endpoint names like unifi_gen_getadopteddeviceoverviewpage. Even within the generated family, verb+resource casing is inconsistent and hard to parse. The surface is not predictable enough for reliable tool selection.

169 tools is far beyond a well-scoped MCP surface and includes many duplicate generated/curated pairs. This volume creates selection noise and maintenance burden rather than a coherent toolkit. The count is an extreme mismatch for practical agent use.

Coverage is broad across networks, Wi-Fi, firewall zones/policies, ACL rules, DNS policies, traffic lists, vouchers, devices, clients, SD-WAN, VPN, and ISP metrics, with many CRUD operations. There are notable dead-end compatibility tools such as unifi_net_block_client and unifi_net_unblock_client that intentionally error, and some resources are read-only, but the overall surface is extensive.