unifi-network-mcp
Related Servers
Alternatives to unifi-network-mcp
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceMCP server for UniFi Network Controller that provides full API coverage for managing APs, clients, WLANs, firewall rules, VLANs, port forwards, and more.51-
- AlicenseNot gradedqualityCmaintenanceA safety-first MCP server for managing UniFi networks, exposing 17 tools for telemetry, diagnostics, and guarded mutations with dry-run previews and confirm requirements.14MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for managing UniFi Network Controllers, providing tools to read and modify network configurations, clients, devices, events, diagnostics, and backups via API key.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server and CLI for UniFi Network controllers: clients, devices, WLANs, firewall, and health over stdio or streamable HTTP, with auth.4AGPL 3.0
- AlicenseAqualityBmaintenanceEnables local UniFi Network inspection and management through MCP, providing typed read-only inventory of sites, devices, clients, and networks, with preview-first, explicitly confirmed device rename and LED locate operations.8MIT
- AlicenseNot gradedqualityAmaintenanceAn MCP server for self-hosted UniFi gateway management, providing tools for devices, networks, WiFi, firewall rules, switch port profiles, connected clients, and a one-shot IoT network creation with rollback.23MIT
TDQS
Scored across 16 tools
Each of the 16 tools targets a distinct UniFi resource domain (devices, networks, firewall policies, WiFi broadcasts, etc.), and the descriptions clearly delineate their purposes. Even the more generic 'unifi_supporting' is explicitly a collection of read-only reference lists, so there is no overlap or ambiguity.
All tools follow a consistent unifi_<resource> naming pattern, and operations consistently use verb_noun style (list, get, create, update, delete). Minor deviations such as 'patch' vs 'update' and 'generate' vs 'create' are isolated and do not undermine the overall predictable convention.
At 16 tools, the server sits just above the typical 3-15 well-scoped range, but the breadth is justified by the complexity of UniFi network management. Each tool covers a meaningful subdomain, so the count feels comprehensive rather than bloated.
The server covers the major configuration and management domains (devices, networks, firewall policies/zones, WiFi broadcasts, vouchers, traffic lists, ACLs, clients) with rough CRUD or lifecycle coverage. Read-only reference data is well represented, and gaps like site creation are likely due to API limitations rather than an incomplete tool surface.