Skip to main content
Glama

Related Servers

Alternatives to py-unifi-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      MCP server providing typed, safety-gated access to UniFi Network consoles via the official API, enabling management of devices, clients, networks, WiFi, firewall policies, and more.
      16
      54 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a curated, scoped, audited MCP surface for managing UniFi Network controllers, offering typed read primitives, stats queries, scoped operational and backup actions, and multi-controller inventories. Change control uses a two-person approval lifecycle with pre-image capture, local validation, and best-effort rollback, since the controller has no candidate configuration or commit step.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A safety-first MCP server for managing UniFi networks, exposing 17 tools for telemetry, diagnostics, and guarded mutations with dry-run previews and confirm requirements.
      16
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable clients to interact with UniFi Site Manager and UniFi Dream Machine telemetry, providing tools for client details, ISP metrics, and more.
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to search, describe, and call roughly 180 undocumented UniFi OS/Network console API operations from a bundled OpenAPI spec, plus curated reads and typed configuration changes. Writes are off by default, require per-entity enablement, and use previews, verification, and rollback safeguards.
      29
      MIT

    TDQS

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: networks, sites, devices, clients, health, device telemetry, device rename, and device locate. There is no meaningful overlap or confusion between tool purposes.

    Naming Consistency5/5

    All tools use the unifi_ prefix followed by a clear verb_noun pattern such as list_networks, get_health, rename_device, and locate_device. The naming is uniform and predictable across the entire set.

    Tool Count5/5

    Eight tools is well-scoped for a UniFi controller MCP server covering inventory lookup, status checks, and common device actions. Each tool serves a clear purpose without unnecessary bloat.

    Completeness4/5

    The tool set covers core UniFi operations well: listing sites, networks, devices, clients, checking health, and retrieving device details. Minor gaps exist, such as no network configuration or additional device management actions, but the main workflows are represented.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues