LabscoMCP early access ↗
teeflooMCP SERVER

AsusWRT MCP Server

Read an ASUS router's real state over SSH — clients and DHCP leases, WAN and DNS configuration, listening ports, wireless radios, cron jobs and conntrack usage — with setting changes locked behind an explicit opt-in.

by teefloo ↗Network, Endpoint & Fleet ManagementCommunity

LABSCO SUMMARY

Reading clients, DHCP leases and ARP neighbours as three separate tools is the tell — whoever built this knows those three lists disagreeing is the actual diagnostic.

A router's client list, its DHCP leases and its ARP table describe the same network and routinely differ: a device with a lease that is not responding, a neighbour with no lease, a client the UI shows that the kernel does not. Collapsing them into one 'devices' tool would lose exactly the signal someone is looking for at two in the morning. The same instinct shows in the SSH diagnostic splitting reachability from banner from authentication, and in a capabilities tool that states its own guardrails up front. Changes are fenced off: the mutation tools refuse to run unless ASUSWRT_ALLOW_MUTATIONS=true is set and the call passes confirm: true, and dry_run: true previews a change first — which for a home router reached by an agent is the right side of the line to be on.

What it is

An ASUSWRT diagnostic client that reaches the router over SSH and reports what it finds, across identity and health, network and addressing, wireless, administrative access, storage, and process and kernel state.

What you get

  • asuswrt_capabilities returns the server's own guardrails and safe settings, so what it will and will not do is knowable before anything else is called.
  • asuswrt_ssh_diagnostics separates TCP reachability, banner exchange and authentication — three different failures that otherwise present as one.
  • The network picture in layers: LAN addressing and DHCP presence, WAN protocol with gateway and DNS, IPv6 prefix and router address, DHCP pool and static reservations, and NVRAM-reported DNS settings.
  • Who is actually on it — connected clients, active dnsmasq leases and ARP neighbours read separately, because they disagree in useful ways.
  • Security-relevant surface: web admin ports and processes, web, SSH and telnet access settings, listening TCP and UDP sockets, loaded kernel modules and scheduled cron jobs.
  • Wireless radios with SSIDs and per-band connection counts, plus guest networks with their LAN-access state.
  • Capacity and storage: per-interface RX and TX counters from the kernel, conntrack table usage against its limit, filesystem usage, mounts and partitions.

Requirements

SSH access to the router, with SSH enabled on it. The monitoring tools only read; the mutation tools stay off unless ASUSWRT_ALLOW_MUTATIONS=true is set.

Setup effort

One command plus credentials — uvx asuswrt-mcp, then supply credentials