UniFi MCP Server
Related Servers
Alternatives to UniFi MCP Server
- AlicenseAqualityBmaintenanceEnables querying UniFi network devices and data using natural language through MCP clients like Claude Desktop.4311 npm1MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage and monitor UniFi network infrastructure through natural language, providing 46 management tools across device, client, WiFi, network, firewall, port forwarding, monitoring, and site management.1MIT
- FlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to UniFi Network and Protect infrastructure for managing devices, monitoring clients, analyzing network health, viewing camera snapshots, and getting optimization recommendations across multiple UniFi controllers.2-
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage UniFi Network, Protect, and Access infrastructure through MCP tools, with support for local controllers and cloud relay.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to inspect and operate UniFi Network and Protect devices on a local console, with configurable read-only, action, or full-control permission tiers.MIT
- 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.9 npmMIT
TDQS
Scored across 111 tools
The descriptions are unusually thorough and cross-reference near-neighbors well, but 111 tools creates many clusters where an agent could easily pick the wrong one. Health summaries, traffic views, Protect event tools, and analysis reports all overlap enough that careful reading is required to avoid misselection.
Names overwhelmingly follow a clear verb_noun pattern such as list_*, get_*, create_*, update_*, delete_*, and set_*. Minor inconsistencies exist: reads mix list_ and get_ arbitrarily, global aggregation uses get_global_* alongside get_all_sites_health, and trigger operations use capture_, poll_, run_, and test_ inconsistently.
With 111 tools, this is a severe count mismatch even for a server covering UniFi Network, Protect, and runtime administration. The tool count far exceeds the 25+ threshold for 'too many' and will overwhelm agent context and increase selection errors.
The surface is remarkably broad, covering CRUD for networks, WLANs, firewall rules/policies, client management, schedules, webhooks, and Protect cameras, plus global aggregation and analysis. Notable gaps include no update for firewall policies or port-forwarding rules and no device adoption/forget lifecycle, but most gaps can be worked around.