Model Context Protocol (MCP) server for secure, controlled administration of AsusWRT and AsusWRT-Merlin routers via SSH.
Asuswrt MCP MCP server exists for a simple reason — assistants are far more useful when they can act on Asuswrt MCP directly instead of describing what you should do. Model Context Protocol (MCP) server for secure, controlled administration of AsusWRT and AsusWRT-Merlin routers via SSH.
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.
Once Asuswrt MCP is connected, these are the calls the assistant has available:
confirm — true parameterCategory — ToolsNetwork — LAN/WAN details, DNS config, IPv6 status, routing tableClients — Connected clients, DHCP leases, ARP neighborsWireless — Radio status, SSIDs, guest networks, client counts per bandServices — Running processes, open ports, cron jobsStorage — USB devices, mounts, partitions, filesystem usageSecurity — UPnP, DDNS, Samba status, conntrack usageVPN — OpenVPN server, WireGuard, VPN client profilesAdministration — Web admin ports, SSH/telnet access settingsDiagnostics — SSH TCP/banner/auth diagnostics, config snapshotasuswrt_restart_service — Restart allowlisted services (httpd, firewall, wireless, dnsmasq, etc.)You will need 3 environment variables: ASUSWRT_HOST, ASUSWRT_SSH_USERNAME, ASUSWRT_SSH_PASSWORD. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Asuswrt MCP's toolset — confirm, Category, Network and 11 more — is a fair guide to whether it matches your workflow. It is maintained by teefloo; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| confirm | true parameter |
| Category | Tools |
| Network | LAN/WAN details, DNS config, IPv6 status, routing table |
| Clients | Connected clients, DHCP leases, ARP neighbors |
| Wireless | Radio status, SSIDs, guest networks, client counts per band |
| Services | Running processes, open ports, cron jobs |
| Storage | USB devices, mounts, partitions, filesystem usage |
| Security | UPnP, DDNS, Samba status, conntrack usage |
| VPN | OpenVPN server, WireGuard, VPN client profiles |
| Administration | Web admin ports, SSH/telnet access settings |
| Diagnostics | SSH TCP/banner/auth diagnostics, config snapshot |
| asuswrt_restart_service | Restart allowlisted services (httpd, firewall, wireless, dnsmasq, etc.) |
| asuswrt_dhcp_server | Enable/disable DHCP server |
| asuswrt_upnp | Enable/disable UPnP |
{
"mcpServers": {
"asuswrt-mcp": {
"command": "C:\\path\\to\\asuswrt-mcp\\.venv\\Scripts\\python.exe",
"args": ["-m", "asuswrt_mcp.server"],
"env": {
"ASUSWRT_HOST": "192.168.1.1",
"ASUSWRT_SSH_USERNAME": "admin",
"ASUSWRT_SSH_PASSWORD": "your_password"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| ASUSWRT_HOST | Endpoint or connection string the server talks to. | Optional |
| ASUSWRT_SSH_USERNAME | Configuration value read at startup. | Optional |
| ASUSWRT_SSH_PASSWORD | Configuration value read at startup. | Optional |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.