fritzbox-mcp
Related Servers
Alternatives to fritzbox-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceA 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 gradedqualityNot gradedmaintenanceEnables interaction with Firewalla network security devices for network monitoring, device management, traffic analysis, and security rule configuration through MCP tools.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to query homelab infrastructure such as Proxmox VE, NetBox, systemd services, Grafana, InfluxDB, AdGuard Home, ping logs, and configured HTTP JSON endpoints through read-only tools.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables LLM/MCP clients to read and, when explicitly allowed, modify TP-Link Archer AX53 router settings directly over the LAN using the router's own web protocol, without a browser or cloud account. It is read-first, write-gated, and lockout-aware, with tools for clients, DHCP, Wi-Fi, access control, presence history, and other router operations.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable clients to interact with UniFi Site Manager and UniFi Dream Machine telemetry, providing tools for client details, ISP metrics, and more.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI copilots and autonomous agents to inspect, diagnose, and safely manage TP-Link 4G/LTE gateways and broadband routers through typed MCP tools for status, signal, clients, Wi-Fi, DNS, SMS/USSD, and guarded mutations. It provides session leasing and confirmation safeguards to avoid locking out admins or disconnecting active sessions.MIT
TDQS
Scored across 10 tools
Most tools have clearly distinct targets (DSL, WLAN, mesh, log, calls, answering machine). The main overlap is between 'geraet' (locate a single device) and 'hosts' (list all known devices with IP/MAC), and secondarily 'wlan_status' vs 'mesh_uebersicht' since mesh reports per-radio data too; descriptions mostly disambiguate these.
Naming follows mainly German compound nouns (dsl_status, wlan_status, mesh_uebersicht, anrufliste) but mixes in a bare singular ('geraet') and a verb-first form ('zugang_pruefen'), plus an inflected compound ('anrufbeantworter_audio'). It is readable and semi-predictable but not a single consistent convention.
10 tools is well-scoped for a FRITZ!Box diagnostic server; each tool maps to a distinct subsystem (access, DSL, WLAN, mesh, devices, log, telephony) and none feel redundant.
The surface covers the main diagnostic domains: connectivity/access, line and radio status, device inventory/lookup, log, and telephony including audio retrieval. Gaps are minor and mostly read-only limitations (e.g. no way to mark AB messages heard or perform actions like reboots/WLAN toggles), which are documented rather than dead ends.