Skip to main content
Glama

Related Servers

Alternatives to fritz-mesh-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      AI assistants diagnose, audit and safely manage AVM FRITZ!Box routers on FRITZ!OS 8: line and network diagnostics, scored security check, devices, Wi-Fi, telephony and smart home. Starts read-only; every change is read back and reported as verified, and reboots, port forwards and firmware updates need a plan, a one-time token and an explicit execute.
      79
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables Claude Code and other MCP clients to inspect and manage a TP-Link router over stdio, including device lists, DHCP leases and reservations, Wi-Fi settings, firmware and IP status, mesh nodes, and safe raw endpoint requests with confirmation for writes and secret masking.
      16
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for interfacing with AVM FRITZ!Box routers. Control smart home devices, monitor network status, and administer your router through any MCP-compatible client.
      10
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables LLM clients to inspect and manage a TP-Link Deco mesh Wi-Fi network, covering mesh nodes, connected devices, SSIDs and radio settings, internet status, blocked clients, and DHCP address reservations. Runs entirely against the router on the local network without any cloud account.
      15
      54 PyPI
      MIT

    TDQS

    B3/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action, and the descriptions proactively disambiguate the risky pairs (band steering vs backhaul steering, reserve_ipv4 vs lan_dhcp, mesh_status vs get_radio). There is still some read overlap: fritz_mesh_status and fritz_get_radio both surface channel mode/power, and fritz_wifi_networks vs fritz_connection_status both touch WAN/Wi-Fi state, so an agent may occasionally pick the broader one.

    Naming Consistency4/5

    All tools share a fritz_ prefix and snake_case, and mutating tools consistently use fritz_set_*/fritz_reserve_*/fritz_reboot. Read tools are mixed, however: some use get_/list_ (fritz_get_device, fritz_list_devices) while others are bare nouns (fritz_wifi_networks, fritz_lan_dhcp, fritz_system_log, fritz_port_forwards), which slightly breaks the pattern predictability.

    Tool Count4/5

    22 tools is on the heavy side but the domain is genuinely broad (mesh/radio, devices, WAN, LAN/DHCP, firewall, WoL, smart home, logs), and each tool corresponds to a real router capability rather than filler. It is close to the point where a grouped read tool would be preferable, but nothing feels redundant.

    Completeness4/5

    Read coverage is strong (status, devices, radio, WAN, Wi-Fi, DHCP, logs, port forwards, smart home) and most config knobs have a setter, including steering, channel, power, guest Wi-Fi, WAN blocking, UPnP, and IP reservation. The main gaps are write-side: port forwarding is list-only (no create/delete rule), and there is no way to change SSIDs/passwords or manage smart-home setpoints beyond a binary switch.