mcp-unifi-network
Related Servers
Alternatives to mcp-unifi-network
No user-submitted related servers found.
Related Servers
- AlicenseDqualityDmaintenanceEnables read-only, bounded access to UniFi Network appliance health, devices, and active clients through three safe MCP tools with TLS verification and redirect rejection.3MIT
- AlicenseBqualityDmaintenanceEnables AI assistants to manage and monitor UniFi Network Controllers through natural language. Provides 25 read-only tools for discovering devices and clients, viewing security configurations, analyzing network statistics, and exporting configuration data.41MIT
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive management of UniFi Network infrastructure through 24 tools for monitoring and controlling devices, clients, wireless networks, security, and guest access. Supports network administration tasks like device restarts, client blocking, WLAN configuration, and backup creation.14 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables read-only querying of a UniFi fleet via the Site Manager API and per-console connector proxy, allowing users to list hosts, sites, devices, ISP metrics, and live network clients through Claude.-
- AlicenseAqualityBmaintenanceExposes the UniFi Network Integration API as tools for managing sites, devices, clients, networks, WiFi, firewalls, ACLs, switching, DNS policies, hotspot vouchers, VPNs, and more.49332 npm2MIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Ubiquiti UISP API for managing network devices, sites, and monitoring through dynamically generated read-only tools.2MIT
TDQS
Scored across 14 tools
Each list_* tool targets a clearly distinct resource (sites, devices, clients, vouchers, networks, WLANS, firewall zones, firewall policies), and get_device vs get_device_stats vs get_client are well separated by their descriptions. The main friction is unifi_auth_status vs unifi_get_console_info, which both diagnose 'why is a tool missing / version mismatch', and the generic unifi_request slightly overlaps every read tool as a fallback.
All tools use a consistent unifi_ prefix with snake_case verb_noun (list_*, get_*, list_firewall_zones), which is easy to scan. Minor deviations are unifi_auth_status (noun phrase) and the bare-verb unifi_request, but neither breaks the pattern.
14 tools is well within the ideal band and each one maps to a distinct resource or diagnostic need; nothing looks redundant or padded. The read-only scope keeps the set tight and every tool earns its place.
The read surface covers the core inventory: sites, devices, device stats, clients, networks, WLANS, vouchers, firewall zones and policies. Gaps exist (no single-site detail, no events/alarms or DPI views, and all mutations are gated behind UNIFI_ALLOW_WRITES), but unifi_request provides a documented GET escape hatch for anything unwrapped.