fritz-mesh-mcp
Related Servers
Alternatives to fritz-mesh-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceAI 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.79MIT
- AlicenseBqualityBmaintenanceEnables 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.16MIT
- AlicenseAqualityDmaintenanceA 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.10MIT
- AlicenseNot gradedqualityCmaintenanceProvides full administrative control of OpenWRT routers via SSH, with a preview-confirm safety model for mutating operations.6 npmMIT
- AlicenseAqualityBmaintenanceEnables 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.1554 PyPIMIT
- AlicenseBqualityBmaintenanceEnables MCP clients to read FRITZ!Box data over TR-064, including mesh, Wi-Fi, devices, logs, DSL, call lists, and voicemail, with optional guarded write actions for configuration changes.10MIT
TDQS
Scored across 22 tools
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.
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.
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.
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.