Skip to main content
Glama
Sign In
mcp-zyxel

mcp-zyxel

by hugil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-zyxel

No user-submitted related servers found.

    Related Servers

    • NetWarden

      danielshaji1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to discover, configure, harden, and troubleshoot multi-brand home and homelab networks through MCP, backed by declarative Terraform/OpenTofu orchestration. Includes safety guardrails, drift detection, snapshots, rollback, and zero-trust device controls.
      MIT

    • 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.
      -

    • tplink-mcp

      dulithdivisekara
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI copilots and autonomous agents to inspect, diagnose, and safely manage TP-Link 4G/LTE gateways and broadband routers through typed MCP tools for status, signal, clients, Wi-Fi, DNS, SMS/USSD, and guarded mutations. It provides session leasing and confirmation safeguards to avoid locking out admins or disconnecting active sessions.
      MIT

    • netdiag-mcp

      chaojiwudipaozi
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to drive switches, servers, and consoles over SSH or serial Console through 28 MCP tools, auto-detecting vendors, paging through long output, and cleaning raw byte streams into readable text. Provides structured diagnostics (interfaces, ARP/MAC/routing tables, ping, logs, health checks) plus a three-tier safety model with audit logging, credential redaction, and dry-run config changes.
      MIT
    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

    ActivityStale
    ResponsivenessNo issues

    Resources