No user-submitted related servers found.
Scored across 24 tools
Each tool targets a distinct resource/action pair, from list_interfaces to move_firewall_rule, so an agent can reliably select the right operation. ros_list is broad but is explicitly framed as a read-only escape hatch, not a competing path.
Most tools follow a clean list_/add_/remove_/set_*_enabled pattern, and the firewall group is especially consistent. A few stragglers like system_info, ros_list, and connectivity_check break the verb-first convention without causing real confusion.
24 tools is at the upper edge of reasonable, but the server spans many distinct MikroTik subsystems: interfaces, firewall, NAT, DHCP, DNS, routes, and logs. Each tool earns a place, and there is little obvious redundancy beyond the intentional ros_list fallback.
Firewall lifecycle is well covered with create, read, update, delete, move, and enable/disable. However, NAT and DNS entries lack update operations, routes are read-only, and ros_list cannot write, so some configuration changes require workarounds or are impossible.