keenetic-mcp
Related Servers
Alternatives to keenetic-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets AI agents control a Keenetic router over the local network through the Model Context Protocol, managing devices, Wi-Fi, port forwarding, KeenDNS, DNS, DHCP, firewall, mesh, storage, logs and diagnostics with a safe, read-back-verified change model. An opt-in SSH mode additionally enables Entware package management and config file editing on the router.1MIT
- AlicenseBqualityCmaintenanceEnables AI agents to manage Keenetic routers through the same RCI API used by the router's web interface, working directly over the local network without cloud involvement. It supports reading device statuses and executing configuration changes, with confirm, dry-run, and destructive-action safeguards.23PolyForm Noncommercial 1.0.0
- AlicenseAqualityBmaintenanceEnables AI clients to perform controlled diagnostics and configuration of Keenetic and Netcraze routers over LAN RCI or remote KeenDNS HTTPS, with read-only mode, guarded writes, and centralized secret masking.19MIT
- AlicenseAqualityBmaintenanceAn 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.10MIT
- FlicenseNot gradedqualityAmaintenanceEnables users to control firewall rules, VPNs, DNS, DHCP, and diagnostics in natural language from MCP clients, with safety guardrails, config backups, and rollback support.-
- AlicenseNot gradedqualityCmaintenanceMCP 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.MIT
TDQS
Scored across 20 tools
Each tool has a distinct resource+action target (routes vs policies vs segments vs interfaces vs devices), and the descriptions explicitly resolve the few naturally overlapping cases — e.g. 'use get_wifi_status rather than list_interfaces', 'uiVisible is the field that matters' for list_segments, and rci_call is documented as the deliberate fallback for everything else. The list_/get_ pairings (list_devices/get_device, list_interfaces/get_interface) are unambiguous summary-vs-detail splits rather than duplicates.
The dominant convention is verb_noun snake_case (get_system_info, list_segments, create_segment, delete_segment, update_device, save_config, backup_config) and it is applied consistently. Minor deviations exist: set_interface_state uses 'set_' where update_device uses 'update_', and ping/traceroute/rci_call are bare verbs or single tokens, though these read naturally as conventional command names.
20 tools is on the heavy side of the 3-15 sweet spot, but for a router administration surface spanning system, routing, Wi-Fi, segments, devices, interfaces, diagnostics and config persistence, each tool maps to a real capability and none looks like filler. Slightly over-scoped rather than bloated.
Strong lifecycle coverage for segments (create/list/delete with rollback and verification) plus a coherent config-safety story (backup_config, save_config, get_config_state) and network diagnostics. Gaps remain: no direct Wi-Fi/SSID credential editing, no interface or tunnel creation, no policy creation, and no reboot/firmware tool — all reachable only via raw rci_call, which is a workable but less safe escape hatch.