tplink-modem-mcp
Related Servers
Alternatives to tplink-modem-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to read and manage a TP-Link Deco mesh router over its local web API, including listing clients, auditing and changing DHCP reservations, renaming devices, viewing traffic and settings, and optionally rebooting the mesh. Router changes require approval, secrets are redacted, and communication stays local without cloud account access.MIT
- AlicenseBqualityDmaintenanceEnables AI agents to manage TP-Link routers by listing clients, checking status, controlling Wi-Fi, and rebooting via natural language.332MIT
- 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 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
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to interact with Xiaomi/Redmi routers, providing read-only queries and management capabilities such as device listing, port forwarding, DHCP reservations, and reboot control.MIT
- AlicenseBqualityBmaintenanceEnables AI assistants and terminal users to inspect and administer TP-Link routers through typed MCP tools, including live LTE signal and cell/band control, connected clients and DHCP reservations, Wi-Fi and LED settings, diagnostics, SMS/USSD, and guarded disruptive actions.39MIT
TDQS
Scored across 17 tools
Most tools target clearly distinct resources or actions (status, clients, DHCP, logs, Wi-Fi, reboot). The main overlap is that router_change can perform any setting change, including the Wi-Fi and static-IP operations handled by set_wifi, set_static_ip, and remove_static_ip; descriptions clarify that the specialized tools are convenience wrappers with plan/confirm behavior, but an agent could still hesitate between the generic and specific paths.
All names use snake_case, which is consistent, but the convention is mixed: some are verb-first (list_clients, find_client, set_wifi, reboot_router) while many are noun-only (wifi_networks, router_logs, dhcp_leases, ipv6_status, client_history) and others are noun+verb (router_read, router_change, router_run). It remains readable, but there is no single predictable verb_noun pattern.
17 tools is slightly above the typical 3–15 range and feels a bit heavy, partly because a generic settings layer (router_objects, router_read, router_change, router_run) coexists with convenience wrappers (set_wifi, set_static_ip, remove_static_ip). Still, each tool maps to a real router-management operation and the breadth of the domain justifies most of them.
The surface covers status, clients, presence history, Wi-Fi, logs, DHCP leases and reservations, IPv6, reboot, and a generic read/change/run layer for any web-UI settings object, which closes most potential gaps. Minor omissions like traffic/bandwidth monitoring or firmware updates are largely reachable through router_objects/router_read/router_change, so there are no obvious dead ends.