mikrotik-mcp
Related Servers
Alternatives to mikrotik-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables management of MikroTik routers running RouterOS 6 and 7 via SSH, Telnet, or API with automatic command adaptation. Provides over 46 MCP tools for device management, firewall, DHCP, VPN, configuration profiles, and more.3MIT
- FlicenseNot gradedqualityCmaintenanceEnables agents to access network device management interfaces via SSH, keeping credentials on the server side. Supports both interactive terminal sessions and command execution on devices like Huawei VRP, MikroTik, and OpenWrt.1-
- AlicenseNot gradedqualityDmaintenanceMCP server that sends CLI commands to MikroTik RouterOS via SSH. It allows executing any RouterOS CLI command and getting text output back.1-
- AlicenseNot gradedqualityAmaintenanceMCP server for managing MikroTik RouterOS fleets, exposing 65+ tools for system administration, interfaces, firewall, DHCP/DNS, PPP, diagnostics, and SSH command execution with KeePass-backed credentials.19 npm2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP agents to control Keenetic routers via plain language, providing network monitoring, device management, and safe configuration changes with backup and read-only options.78 npm24MIT
- AlicenseNot gradedqualityAmaintenanceTurns a MikroTik router into 310 MCP tools for AI-driven configuration over SSH, covering firewall, routing, VPN, and more.523 npm16MIT
TDQS
Scored across 2 tools
mikrotik_list_profiles and mikrotik_exec have completely distinct purposes: one discovers connection profiles, the other executes RouterOS commands. The descriptions even cross-reference each other, making misselection very unlikely.
Both tools share a consistent mikrotik_ prefix and use snake_case, which is good. However, list_profiles follows a verb_noun pattern while exec is a bare verb without an object, a minor style inconsistency.
At two tools, the count is slightly below the typical 3-15 range, but the split is sensible: one tool for discovery and one for execution. Each tool earns its place for the server's narrow purpose.
For a server whose stated purpose is running RouterOS commands on configured profiles, the surface is complete: discover profiles, then execute commands. There are no obvious missing operations, and the stateless/read-only behavior is handled clearly.