Skip to main content
Glama
hugil

mcp-zyxel

by hugil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-zyxel

No user-submitted related servers found.

    Related Servers

    • hpe-cx-mcp

      legalla
      F
      license
      Not graded
      quality
      B
      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.
      -

    • vigor3912s-mcp

      jooservices
      A
      license
      C
      quality
      A
      maintenance
      Enables AI assistants to operate a DrayTek Vigor 3912S router through the full DrayOS CLI, with read-only tools by default and two-step confirm-gated writes. It also provides SQLite audit logging and safety controls like host-key pinning and command blocklists.
      217
      MIT

    • keenetic-mcp

      salatmaster
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP agents to control Keenetic routers via plain language, providing network monitoring, device management, and safe configuration changes with backup and read-only options.
      18
      289 npm
      27
      MIT

    • keenetic

      Kykyryky23
      F
      license
      B
      quality
      A
      maintenance
      Enables AI agents to manage Keenetic routers through the same RCI API used by the router's web interface, working directly over the local network without cloud involvement. It supports reading device statuses and executing configuration changes, with confirm, dry-run, and destructive-action safeguards.
      23
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools target clearly distinct resources or actions (e.g., each get_*_config covers a different switch feature, and create/delete/list/set VLAN tools are well separated). Minor potential confusion between backup_config (running config as file) and get_running_config_text, or between sync_snapshot and sync_to_github, but descriptions clarify the difference.

    Naming Consistency4/5

    Names follow a consistent snake_case verb_noun pattern (get_*, set_*, create_*, delete_*, list_*), with readable abbreviations. Slight deviations like the bare 'reboot' and 'get_pvids' (plural noun rather than get_pvid) are minor and do not hinder predictability.

    Tool Count3/5

    26 tools is on the heavy side for a switch management server. Many read-only feature getters (get_lag_config, get_loopguard_config, get_lldp_config, etc.) could be consolidated into a parameterized config getter, though each does cover a distinct feature.

    Completeness3/5

    Core VLAN CRUD, port configuration, and backup/sync workflows are covered. However, many features (STP, LLDP, LAG, loop guard, syslog, mirror, port security) are read-only with no corresponding setters, which is a notable gap for a switch configuration server.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources