Skip to main content
Glama
legacy-switch-mcp

legacy-switch-mcp

Related Servers

Alternatives to legacy-switch-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read TP-Link Easy Smart switches through their web UI, covering ports, link speeds, counters, VLANs, and other settings, and to audit for cabling, duplex, speed, VLAN, and configuration issues without changing the switch.
      MIT
    • 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 clients to run allow-listed show commands and fixed, safety-gated configuration actions—such as port admin state, PoE, descriptions, and saving config—on a single Linksys LGS-series switch over SSH.
      11
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and change MikroTik SwOS / SwOS Lite switches live over their web API, with field maps learned from each switch, safe dry-run and confirm writes, and .swb backup decoding, diffing, and restore.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI clients to safely read and configure Zyxel GS1900 smart-managed switches via typed MCP tools with guardrails like dry-run, auto-backup, and protected ports.
      26
      1
      MIT

    TDQS

    B3.1/5.0

    Scored across 13 tools

    Disambiguation3/5

    discover vs probe are clearly distinct (broadcast on an interface vs targeted IP query), but overview and get_state overlap significantly—overview for D-Link returns 'the parsed state' which is also get_state's stated purpose. Similarly list_snapshots and list_files both enumerate saved files, requiring careful reading to distinguish.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (list_switches, get_state, backup_config, describe_switch), but discover, probe, and overview are bare verbs/nouns, creating minor inconsistency. The convention is still readable and predictable overall.

    Tool Count5/5

    13 tools is well-scoped for a switch management server covering discovery, inspection, and backup. Each tool appears to earn its place in the workflow without excessive granularity.

    Completeness3/5

    The surface is rich for read-only inspection and backup (discovery, state parsing, config/firmware backup, snapshots, wiki descriptions), but lacks any mutation or apply operations despite list_snapshots referencing 'the snapshot before every apply.' Agents cannot change switch configuration, a notable gap for a management server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues