
Asuswrt Mcp
io.github.teeflooPublished by GitHub account teefloov0.1.1Updated Oct 24, 2026
Secure AsusWRT router administration via SSH — 42+ tools, guarded mutations
Overview
Lets an assistant monitor and, when explicitly enabled, change settings on an AsusWRT or AsusWRT-Merlin router over SSH.
- What you can do
- Provides 42 read-only tools covering router identity and health, LAN/WAN and DNS configuration, connected clients and DHCP leases, wireless radios and guest networks, running services and open ports, storage, security features, VPN status, and SSH diagnostics. Optional mutation tools can restart allowlisted services, toggle DHCP, UPnP, Wi-Fi radios and guest networks, manage port forwarding, OpenVPN server, parental controls, and DHCP reservations. Mutations require an explicit confirm parameter and support dry-run previews.
- When to use it
- Useful when you want an assistant to inspect a home or small-office Asus router's status, clients, wireless, VPN, or security settings without logging into the web interface. Add it if you also want guided, guarded changes such as restarting a service or adjusting guest Wi-Fi, port forwarding, or parental controls.
- Requirements
- Runs locally as a Python package (Python 3.11+) over stdio. Needs network reachability from the machine to the router and SSH access enabled on the router. Required environment variables: ASUSWRT_HOST, ASUSWRT_SSH_USERNAME, and either ASUSWRT_SSH_PASSWORD or ASUSWRT_SSH_KEY_FILE. Mutations additionally need ASUSWRT_ALLOW_MUTATIONS set to true.
Installation
In SourceWeft
- Open Asuswrt Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
AsusWRT MCP Server
[Python 3.11+] [MIT License] [Project Status: Active]
mcp-name: io.github.teefloo/asuswrt-mcp
Model Context Protocol (MCP) server for secure, controlled administration of AsusWRT and AsusWRT-Merlin routers via SSH.
Overview
This MCP server provides AI assistants (like Claude, Cursor, etc.) with a safe interface to monitor and manage AsusWRT routers. It operates exclusively over SSH using allowlisted operations—no arbitrary command execution, no firmware modifications, and no factory resets.
Features
Read-Only Monitoring (42 tools)
Mutation Tools (with safety guards)
All mutation tools require:
confirm: trueparameterASUSWRT_ALLOW_MUTATIONS=trueenvironment variable- Support for
dry_run: trueto preview changes
Safety Model
- No arbitrary SSH: Only allowlisted commands are executed via NVRAM and service calls
- No firmware operations: No flash, reset, or bootloader access
- Secret redaction: Passwords and sensitive data are never exposed in tool responses
- Dry-run support: Every mutation can be previewed before applying
- Confirmation required: Mutations require explicit
confirm=True - SSH-only transport: No exposure of the router's web API
Prerequisites
- Python 3.11+
- An AsusWRT or AsusWRT-Merlin router with SSH access enabled
- Network connectivity from the MCP client to the router
Installation
1. Clone and setup
2. Configure environment
3. Configure .env
Usage
Run the MCP server
Configure in Claude Desktop / Cursor
Add to your claude_desktop_config.json:
Using with npx Inspector (development)
Development
Run tests
Run with live router integration tests
Project Structure
License
MIT License - see LICENSE for details.
Acknowledgments
- asusrouter for the underlying Python library
- MCP for the protocol specification
- AsusWRT-Merlin for the firmware
Source: README.md at commit 4651689
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts