netmiko-mcp
Related Servers
Alternatives to netmiko-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceTelnet-based MCP server for H3C network device CLI, enabling connection, command execution, and device mode detection via natural language.14-
- AlicenseAqualityDmaintenanceA comprehensive MCP server for network device management via SSH/Telnet. Supports multiple vendors such as Cisco IOS and BDCOM, enabling AI assistants to execute commands and manage routers, switches, and firewalls.4MIT
- FlicenseAqualityBmaintenanceEnables management of multiple MikroTik RouterOS devices over SSH via two tools: device listing and command execution.2-
- FlicenseNot gradedqualityCmaintenanceEnables executing Cisco CLI commands on network devices over SSH through two MCP tools for exec and config commands, with security and automation features.-
- AlicenseAqualityCmaintenanceEnables managing multiple remote Linux hosts over SSH via MCP, with command execution, SFTP file operations, and Windows DPAPI-protected credentials.101MIT
- FlicenseAqualityCmaintenanceEnables control of network switches via serial console ports, supporting Huawei, H3C, and Cisco devices for command execution and configuration.6-
TDQS
Scored across 2 tools
list_devices and run_command have clearly distinct purposes: one enumerates available devices, the other executes commands on a target device. There is no overlap or ambiguity between them.
Both tool names follow the same verb_noun pattern: list_devices and run_command. The naming is consistent, predictable, and easy for an agent to reason about.
With only two tools, the server feels minimal and is at the thin end of the scale. The tools are essential and earn their place, but the surface is quite sparse for a network automation MCP.
The combination of listing devices and running arbitrary read/config commands covers the core Netmiko workflow well. Minor gaps exist, such as no dedicated multi-device execution or explicit save/commit operation, but agents can work around these via run_command.