mikrotik-mcp
Related Servers
Alternatives to mikrotik-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to safely inspect fleets of MikroTik RouterOS devices and SNMP v2c endpoints through deny-by-default read-only tools, batch queries, and one-call diagnosis recipes for NOC work. Returns redacted, auditable results so routers can be observed without any risk of configuration changes.26 npmApache 2.0
- AlicenseBqualityCmaintenanceEnables Claude and other MCP-compatible AI assistants to monitor and configure RouterOS routers and switches over the REST API for v7 or the binary API for v6/v7. Supports status checks, interfaces, routes, firewall rules, DHCP leases, Wi-Fi clients, logs, diagnostics, backups, and configuration changes with read-only and per-device safety controls.221MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to audit, inspect, and safely configure MikroTik RouterOS v7 routers through tools for connection testing, system status, security audits, firewall mangle management, routing, DHCP leases, sanitized exports, containers, and adlist queries.239 npmGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to read, query, and safely modify RouterOS 7 devices over the REST API, covering firewall, routing, DHCP, DNS, interfaces, containers, files, and diagnostics, with confirmation gates and a scheduled rollback guard in front of disruptive changes.46 PyPIMIT
- 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
- AlicenseAqualityBmaintenanceEnables AI agents and NOC staff to inspect TR-069 devices, tasks, faults, files, presets, and provisions through strictly read-only GenieACS NBI GET calls. Secrets and credentials are redacted, with bounded queries and policy guardrails that block write operations before any network request.828 npmApache 2.0
TDQS
Scored across 12 tools
Most tools map to a distinct resource (identity, routerboard, interfaces, IP addresses, routes, ARP, DHCP leases, filter vs NAT rules, logs). The only mild overlap is between get_system_resource and get_system_routerboard, both of which return hardware/system-level information, though the descriptions do differentiate CPU/memory vs board/serial/firmware.
All tools consistently use the mikrotik_ prefix followed by a verb_noun pattern, which is predictable and readable. The only minor deviation is inconsistent use of get vs list for collection endpoints (mikrotik_list_interfaces but mikrotik_get_ip_addresses), which is semantically meaningful but not strictly uniform.
Twelve tools is well within the ideal 3-15 range and each one targets a concrete, commonly needed piece of router telemetry. No tool feels redundant or padding the surface.
The surface is a coherent read-only inspection set covering system, interfaces, IP, routing, ARP, DHCP, firewall and logs, but it offers zero write operations (no creating/disabling interfaces, adding firewall or NAT rules, IP addresses, or DHCP leases), so any remediation workflow dead-ends. Notable read gaps also exist, such as DNS settings, wireless/registration tables, and interface traffic statistics beyond the details call.