tplink-mcp
Related Servers
Alternatives to tplink-mcp
No user-submitted related servers found.
Related Servers
- 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
- 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.1533 PyPIMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to monitor and control Nokia G-2425G-A GPON home routers (e.g., Airtel) via natural language, including listing connected devices, and blocking or unblocking internet access for specific devices.3MIT
TDQS
Scored across 33 tools
The Wi-Fi read surface is split across wifi_info, get_wifi_radio, get_wireless_advanced, and router_status with overlapping SSID/security/txpower/MU-MIMO fields; set_wireless_advanced vs set_wireless_syspara also require close reading. Descriptions are detailed enough to resolve most cases, so overlap exists but is usually manageable.
Most names are snake_case and action-oriented, but the set mixes verb_noun patterns (get_firmware_info, list_clients, set_wifi_band) with noun-only names (router_status, wifi_info, dhcp_leases, ethernet_ports, session_info). It remains readable, but there is no single predictable naming convention throughout.
33 tools is beyond the 25-tool threshold and many are granular setters (set_ofdma, set_twt, set_smart_connect, set_wireless_syspara) that could plausibly be consolidated. The router domain is broad, but the tool surface feels heavy for what an agent can reliably select among.
Core Wi-Fi, DHCP, client diagnostics, reservations, and reboot workflows are covered, and raw_request/list_endpoints provide an escape hatch. However, common router administration areas like port forwarding, firewall/MAC filtering, LAN settings, VPN/QoS, and device blocking are absent as first-class tools.