Keenetic NOC MCP
Related Servers
Alternatives to Keenetic NOC MCP
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables 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
- 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.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.18208 npm28MIT
- AlicenseDqualityBmaintenanceEnables managing MikroTik RouterOS devices via natural language, with read-heavy network inspection and guarded write access across multiple routers.261Apache 2.0
- AlicenseCqualityAmaintenanceEnables AI assistants to operate a DrayTek Vigor 3912S router through the full DrayOS CLI, with read-only tools by default and two-step confirm-gated writes. It also provides SQLite audit logging and safety controls like host-key pinning and command blocklists.217MIT
- 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.208 npmMIT
TDQS
Scored across 19 tools
Most tools map cleanly to a resource and action, e.g. list_devices vs get_device and list_routes vs list_policies. A few pairs overlap: list_vpn vs get_vpn, list_interfaces vs get_interface vs get_wifi_status, and get_connection_status could be mistaken for internet connectivity rather than RCI reachability, though the descriptions do clarify these cases.
The set mostly follows a predictable get_/list_ pattern where list_ means collections and get_ means a specific item or status. Minor deviations exist: list_vpn is singular while sibling tools are plural, and backup_config/rci_call use imperative verbs outside the get/list convention.
19 tools is somewhat heavy, but the router domain genuinely spans devices, interfaces, VPN, Wi-Fi, routes, policies, DNS, logs, and configuration. The count is justified; only mild overlap between interface and VPN tools keeps it from being perfectly scoped.
The read-only monitoring surface is broad: internet, DNS, Wi-Fi, interfaces, VPN, routes, policies, devices, logs, and config backup. There is no dedicated restore/reboot/update tool, but the raw rci_call covers arbitrary commands, so the main gap is convenience operations rather than missing capability.