MikroTik MCP
Related Servers
Alternatives to MikroTik MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA bridge between AI assistants and MikroTik RouterOS devices, allowing natural language interaction to manage network configurations including VLANs, firewalls, DNS settings, and more.1MIT
- AlicenseNot gradedqualityCmaintenanceBridges AI assistants with MikroTik RouterOS devices, enabling natural language management of network configurations, firewall, VLANs, VPNs, and diagnostics via ~300 tools.1MIT
- AlicenseNot gradedqualityCmaintenanceProvides read-only (with limited address-list management) access to MikroTik RouterOS routers, enabling monitoring of system info, interfaces, DHCP leases, firewall rules, and more via natural language.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables natural language management of MikroTik routers through Cursor IDE by translating requests into RouterOS commands via API or SSH.4MIT
- AlicenseDqualityCmaintenanceEnables managing MikroTik RouterOS devices via natural language, with read-heavy network inspection and guarded write access across multiple routers.261Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with MikroTik RouterOS devices through API and SSH connections, supporting network monitoring, configuration management, and diagnostics across multiple routers with automatic connection fallback.3MIT
TDQS
Scored across 239 tools
Tools are organized into clearly named parallel families (filter/raw/nat, IPv4 vs IPv6, wireguard interface vs peer, simple queue vs queue tree), so an agent can generally tell them apart. The main ambiguity comes from the cluster of overlapping log tools (get_logs, get_logs_by_severity, get_logs_by_topic, search_logs, get_system_events, get_security_logs) and eight dead 'Legacy function - not supported in RouterOS v7.x' wireless tools that serve no purpose and add noise.
The dominant pattern is a clean verb_noun scheme (list_x, get_x, create_x, update_x, remove_x, enable_x, disable_x, move_x) applied uniformly across firewall, DHCP, DNS, routes, queues, and WireGuard. The only real deviation is the inconsistent use of add_ vs create_ for creation (add_ip_address, add_route, add_user, add_wireguard_peer vs create_vlan_interface, create_dhcp_server, create_filter_rule), plus a few bare action names like ping, torch, traceroute.
239 tools is an extreme mismatch for any single MCP surface; even a full RouterOS domain does not justify this many, and the set is bloated by eight explicitly unsupported legacy wireless tools and near-duplicate log tools. The breadth pushes far past the point where an agent can reliably select a tool.
Core object lifecycles (firewall filter/raw/NAT, address lists, DHCP server/pool/network, DNS, routes, queues, WireGuard, VLANs, bridge VLANs/ports, IP pools/addresses, users) are covered thoroughly with create/read/update/delete plus enable/disable. However, notable gaps remain: IPsec is read-only (peers, policies, proposals, profiles cannot be created or edited), scripts/schedulers/netwatch are list-only, and there is no bridge creation, DHCP client, PPP/PPPoE server, certificate, SNMP, or device reboot/upgrade tooling.