opus-tplink-mcp
Related Servers
Alternatives to opus-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
- 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
- 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
- AlicenseNot gradedqualityDmaintenanceEnables automation and management of TP-Link BE3600 routers through browser automation, supporting port forwarding configuration, network status monitoring, and device management without reverse-engineering the router's encryption.2MIT
- AlicenseAqualityBmaintenanceEnables an AI assistant to inspect and manage a TP-Link router or ISP modem on the local network, including connected devices, Wi-Fi, fixed IPs, port forwarding, logs, and other web-panel settings. Every change is previewed and only applied after user approval.17GPL 3.0
TDQS
Scored across 33 tools
Most domain-specific tools are distinct, but router_status, router_get, router_catalog, and router_raw_read overlap heavily for read access, and broad multi-action tools like system, lan, wifi_extra, and router_raw_write can shadow specific tools. Descriptions help, but an agent still faces real selection ambiguity.
All names use snake_case, but the patterns are mixed: some are verb_noun or noun_verb forms such as router_status, dhcp_server_set, and wifi_set, while many are bare domain nouns like upnp, mesh, system, internet, lan, and clients. The set is readable but not predictable.
With 33 tools, the surface is heavy and exceeds the typical well-scoped range; several tools could likely be consolidated under broader domain actions. This is not an extreme mismatch for such a feature-rich router, but 25+ tools is too many for easy agent navigation.
Coverage is broad: WAN/LAN, Wi-Fi, DHCP, routing, VPN, mesh, parental/access control, port forwarding, USB, logs, DDNS, extender, maintenance, and raw escape hatches are all present. Minor gaps remain, such as unverified extender writes, disabled mesh pairing, and no per-mapping UPnP delete, but workarounds are documented.