A
licenseA
qualityB
maintenanceAn MCP server that lets an AI assistant manage your Keenetic router in plain language — list connected devices, pin static DHCP leases, rename devices, check WAN status, and reboot.
10
MIT
keenetic-mcp
by st412m
Related Servers
Alternatives to keenetic-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server that bridges AI assistants like Claude Code to Keenetic routers, enabling natural language control of Wi-Fi, devices, VPN, and network segmentation via the router's RCI interface.142 npmMIT
- AlicenseAqualityDmaintenanceMCP server for monitoring and controlling WiFi routers (OpenWrt) via SSH, enabling device listing, status checks, WiFi configuration, rebooting, and more.717 npmMIT
- AlicenseBqualityAmaintenanceCommunity-maintained downstream MCP server for bounded AsusWRT and AsusWRT-Merlin administration over SSH.68MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for querying connected WiFi devices from MikroTik RouterOS, enriched with DHCP leases and ARP table entries.MIT
- AlicenseAqualityAmaintenanceEnables MCP agents to control Keenetic routers via plain language, providing network monitoring, device management, and safe configuration changes with backup and read-only options.18142 npm26MIT
TDQS
B3.3/5.0
Scored across 49 tools
Disambiguation4/5
Most tools target distinct resources or actions, and descriptions actively clarify subtle overlaps such as get_dhcp_static vs get_dhcp_leases, get_config vs rci_query, and get_keendns_mappings vs get_web_access. A few boundaries remain potentially confusing, especially around config-state reads, DNS proxy/host reads, and the many client/device listing tools, but an agent can usually disambiguate from the descriptions.
Naming Consistency4/5
The set is overwhelmingly snake_case with predictable verb_noun or verb_noun_noun forms such as get_clients, set_port_forwarding, remove_dns_host, and backup_config. Minor deviations like reboot, rci_query, and test_watch_rule keep it from being perfectly uniform, but the pattern is still easy to follow.
Tool Count2/5
49 tools is heavy for a single router-management server and exceeds the range where each tool clearly earns its place. Many read-only monitoring tools could be consolidated or grouped, making the surface harder to scan despite the domain being broad.
Completeness3/5
The server covers a strong read surface and has CRUD for port forwarding, KeenDNS mappings, DHCP reservations, DNS hosts, and client registration/blocking, plus backups. However, notable write gaps remain: firewall rules are readable but not editable, and WiFi, VPN, schedule, firmware update, and package-management configuration lack dedicated write tools.
Maintenance
ActivityActive
ResponsivenessNo issues