unifi-mcp
Related Servers
Alternatives to unifi-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceAn MCP server to manage your UniFi network via Claude, providing tools to list devices and clients and block/unblock clients. It runs as a Docker container and is designed for local network use only.-
- AlicenseAqualityDmaintenanceMCP server that turns Claude into a UniFi network specialist. Manage devices, optimize WiFi, audit security, and troubleshoot your network through natural language.3114 npm2MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables AI assistants to manage UniFi network infrastructure, including cloud management, local network devices, and Protect cameras, through natural language.621MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that enables Claude to manage Ubiquiti UniFi networks via the official API, including device/client oversight, network and WiFi configuration, firewall and ACL management, and guest access controls.40 npmMIT
- AlicenseCqualityCmaintenanceA Model Context Protocol (MCP) server for UniFi Network Controllers that enables LLMs to interact with UniFi infrastructure for monitoring and control.51MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for UniFi Network Controller enabling AI assistants to manage UniFi infrastructure via natural language. It supports firewall rules, IPv6, and uses lazy/eager tool modes to minimize context usage.6Mozilla Public 2.0
TDQS
Scored across 58 tools
Descriptions are unusually disciplined about boundaries, explicitly steering between lookalikes (list_clients vs list_known_clients vs list_client_sessions, firewall_rules vs firewall_policies, routes vs traffic_routes, port_forwards vs nat_rules, check_updates vs firmware_status vs system_info). A few clusters remain easy to confuse at a glance — four separate 'policy' listers (firewall_policies, traffic_rules, oon_policies, qos_rules) and get_site_health vs get_dashboard overlap — but the text resolves them.
Every tool uses the unifi_ prefix plus a consistent verb_noun form (get_, list_, check_), with predictable noun phrasing for the resource. No camelCase or verb-style mixing anywhere in 58 tools.
58 tools is far beyond a well-scoped surface; even for a broad UniFi controller domain, the read-only listing surface is heavily fragmented (many one-purpose listers that could be folded into filtered queries). Selection cost per task is high even though each tool technically earns a distinct slice.
The surface is essentially read-only: get_/list_/check_ cover inspection thoroughly, but there is no create, update, delete, block/unblock, restart, or config-mutation tool for clients, WLANs, networks, firewall rules, or backups. An agent can diagnose the controller but cannot act on it, which is a major gap for a UniFi management server.