Skip to main content
Glama
netmiko-mcp-linksys

netmiko-mcp-linksys

by WackEarl

Related Servers

Alternatives to netmiko-mcp-linksys

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-capable AI agents to observe, troubleshoot, and configure Aruba CX (AOS-CX) switches through REST and SSH, with safety controls, inventory management, and verification workflows.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants and other MCP clients to run validated diagnostic and administrative commands on remote Linux servers over SSH, with per-client authentication, server scoping, command validation, and structured audit logging.
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables SSH interactive session management through MCP, supporting commands, menus, and session lifecycle operations.
      1
      -
    • F
      license
      A
      quality
      D
      maintenance
      Enables LLMs to run read-only show commands on Cisco IOS/IOS-XE and Nexus switches over SSH, with a two-account model for privilege separation and a fail-closed allowlist for safety.
      25
      -
    • A
      license
      A
      quality
      B
      maintenance
      Lets an MCP client read port, statistics, VLAN and PoE status from TP-Link Easy Smart switches and, when explicitly gated, power-cycle a wedged PoE camera over the LAN without opening the switch's web UI. It talks the switch's HTML/cgi protocol directly, with double-gated writes, dry-run, protected ports, and lockout-aware failure handling.
      13
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP agents to run RouterOS commands on MikroTik routers over SSH, with configurable profiles, secure authentication, and a read-only safety guard.
      3
      16 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools target a distinct resource+action (poe_set vs port_set_admin_state vs port_set_description are clearly separated), and the read/write SNMP view tools are explicitly differentiated. The only real overlap is show vs port_overview, which run the same filtered show commands — one single, one bundled — mitigated by clear descriptions.

    Naming Consistency3/5

    Everything is snake_case, but the ordering convention is mixed: verb_noun (save_config), noun_verb (poe_set, port_overview), and noun_verb_noun (port_set_admin_state, port_set_description). The snmp_* family is consistent resource_action, so the set is readable but not predictable.

    Tool Count5/5

    Eleven tools sit squarely in the well-scoped band, with each tool earning its place: read-only observation, save, three port mutations, and a small SNMP view/community/user group. No tool appears redundant or trivial.

    Completeness3/5

    Read, save, PoE, port state/description, and SNMP view/community creation are covered, but lifecycle coverage is asymmetric: snmp_user_remove and snmp_community_remove exist with no user-create or view-remove counterpart. Common switch operations (VLAN, reboot, interface speed/duplex) are absent, so agents will hit dead ends outside the narrow surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues