Skip to main content
Glama
enuno

UniFi MCP Server

by enuno
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to UniFi MCP Server

No user-submitted related servers found.

    Related Servers

    • UniFi MCP Server

      vandreus
      A
      license
      D
      quality
      D
      maintenance
      Enables comprehensive management of UniFi network infrastructure through the UniFi Cloud API, including device control, client management, camera settings, and access door control through natural language.
      39
      18 npm
      Apache 2.0

    • UniFi Network MCP Server

      Ruashots
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage UniFi network infrastructure through 50+ tools covering devices, clients, networks, WiFi, firewall rules, and guest access using the official UniFi Network API.
      52
      50 npm
      5
      MIT

    • UniFi MCP

      devjourney
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to manage UniFi Network, Protect, and Access infrastructure through MCP tools, with support for local controllers and cloud relay.
      MIT

    • UniFi Network MCP Server

      CamoRageaholic1
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.9/5.0

    Scored across 43 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, with groups like connector_network_* and connector_protect_* differentiated by HTTP method and target. Integration API list/get tools are distinguished by resource type. However, some overlap exists between site-level tools (e.g., compare_site_performance vs get_cross_site_statistics) and between get_isp_metrics vs query_isp_metrics, though descriptions help disambiguate.

    Naming Consistency3/5

    Naming follows patterns within subgroups (connector_* method, integration list/get), but across the server there is inconsistency: mix of verb_noun (list_sites, get_host), compound names (list_all_sites_aggregated), and non-verb forms (health_check). No single convention is applied globally.

    Tool Count3/5

    43 tools is on the high side for a single server, covering many sub-domains (Network, Protect, Integration, SD-WAN, ISP). Some redundancy exists (multiple site-listing tools) and raw connector proxies add to count. The number feels slightly bloated but still manageable for a comprehensive UniFi interface.

    Completeness3/5

    The server covers a wide range of UniFi functionality: site management, device/client listing, monitoring, SD-WAN, and raw API access via connectors. However, high-level CRUD operations for core entities (sites, devices, clients) are missing; these are only available through raw connector proxies. Gaps exist for user management and configuration write operations via dedicated tools.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources