Skip to main content
Glama
teefloo

AsusWRT MCP Server

by teefloo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to AsusWRT MCP Server

No user-submitted related servers found.

    Related Servers

    • iStoreOS MCP Server

      beck-8
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to read-only monitor iStoreOS/OpenWRT routers via SSH or HTTP/ubus API, providing 31 tools for system status, network info, logs, and plugin status (OpenClash, Passwall, AdGuardHome, etc.).
      31
      MIT

    • OpenWRT SSH MCP Server

      jsebgiraldo
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to manage OpenWRT routers remotely via SSH, supporting system monitoring, network management, OpenThread Border Router configuration, and package management through natural language commands.
      19
      16
      MIT

    • ssh-mcp-server

      ZachFlint
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to securely execute remote SSH commands, perform file transfers, and monitor system status through a standardized interface. It features robust security controls including command whitelisting, blacklisting, and credential isolation to prevent unauthorized operations.
      10
      9 npm
      MIT

    • router-ssh-mcp

      LianXia233
      A
      license
      A
      quality
      C
      maintenance
      Enables managing services on OpenWrt, ImmortalWrt, and systemd-based routers via SSH, with read-only service listing, status, and log queries, plus write operations (start/stop/restart) requiring confirmationional confirmation and an optional shell execution capability.
      8
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 47 tools

    Disambiguation5/5

    All 47 tools have distinct names and clearly separated purposes, from inspecting specific subsystems (ARP, DNS, DHCP) to controlling actions (enable/disable, toggle). Even closely related tools like guest_networks, guest_wifi, and guest_lan_access target different aspects of guest Wi-Fi management.

    Naming Consistency5/5

    Every tool follows the consistent pattern 'asuswrt_<noun_or_noun_verb>' with snake_case. The prefix unifies the set, and the suffixes are descriptive and predictable (e.g., _status, _config, _details, _enable, _disable).

    Tool Count2/5

    47 tools is excessive for a single MCP server. While the domain of router management is broad, many tools are highly granular (separate tools for DHCP config, leases, reservations, and server), leading to bloat. The server would benefit from consolidation or splitting into sub-servers.

    Completeness4/5

    The tool set covers an extensive range of router features: network configuration, wireless, guest networks, VPN, port forwarding, parental controls, system health, and more. Minor gaps exist (e.g., no firmware update or QoS control), but the surface is comprehensive for routine monitoring and administration.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources