AsusWRT MCP
Related Servers
Alternatives to AsusWRT MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server for monitoring and controlling WiFi routers (OpenWrt) via SSH, enabling device listing, status checks, WiFi configuration, rebooting, and more.717 npmMIT
- AlicenseNot gradedqualityBmaintenanceMCP server for full control of STB (Amlogic S9xx / Armbian) via SSH, enabling shell commands, file management, Docker operations, AdGuard Home configuration, and system monitoring.19 PyPIMIT
- AlicenseNot gradedqualityDmaintenanceEnables management of ASUS routers running Asuswrt-Merlin firmware via SSH/SCP. Supports system monitoring, device management, WiFi control, service restarts, NVRAM operations, file transfers, VPN management, and custom command execution.13MIT
- AlicenseBqualityAmaintenanceMCP server for Keenetic routers that runs on the router itself via Entware: clients, DHCP, Wi-Fi, VPN, logs, port forwarding and DNS records, with dry-run by default on every write. A background watcher calls out from the router when a log or config rule matches.494MIT
- AlicenseNot gradedqualityDmaintenanceSSH-based MCP server that enables remote execution of SSH commands, file transfers, and secure server management via the MCP protocol.ISC
- AlicenseBqualityAmaintenanceMCP server enabling local network interaction, shell command execution, system resource monitoring, and SSH-based remote device management.18MIT
TDQS
Scored across 68 tools
Each tool targets a distinct router subsystem or action, and descriptions clearly scope them (e.g., DNS config vs. DNS filter vs. DNS privacy). However, the sheer number of similar status tools (e.g., multiple wireless and VPN statuses) increases the chance of misselection for broad queries.
All tools use the `asuswrt_` prefix and snake_case consistently, with clear, descriptive suffixes. The pattern is predictable across both read-only inspection and write/toggle tools.
68 tools is far beyond the typical range for a cohesive MCP server. While the router domain is complex, many status tools could be consolidated into fewer parameterized calls, making the set unnecessarily heavy and harder to navigate.
The surface covers a wide range of router management areas—network, wireless, firewall, VPN, DHCP, DNS, storage, logging, and parental controls—with both read and write operations. Minor gaps exist (e.g., no firmware upgrade or full QoS rule management), but core workflows are well supported.