Skip to main content
Glama
Heaxu

ensp-mcp

by Heaxu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ensp-mcp

No user-submitted related servers found.

    Related Servers

    • Simon-Ensp-Mcp-Pro

      cg689
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to programmatically generate Huawei eNSP .topo files that include USG6000V firewalls and S3700 switches, and then, once devices are started in eNSP, deliver configurations, run verification, and diagnose faults over Telnet. Ships with one-click health self-checks and topology-generation skills for natural-language-driven lab setup.
      31
      MIT

    • ENSP-MCP AI

      dawnight0x
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI clients to manage Huawei eNSP simulated network devices, execute CLI commands, apply configurations, and perform network diagnostics through natural language, with topology upload and visualization via a web UI.
      3
      -

    • eNSP-MCP

      jmsgfc
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing Huawei eNSP network simulation experiments, enabling topology management, Telnet device interaction, configuration deployment, and verification through natural language or API.
      26
      -

    • ensp-mcp

      loiilp
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to automate management and configuration of Huawei eNSP virtual network devices via Telnet, supporting device discovery, command execution, status query, and network diagnostics.
      -

    • console-switch-mcp

      yangyu2729
      F
      license
      A
      quality
      C
      maintenance
      Enables control of network switches via serial console ports, supporting Huawei, H3C, and Cisco devices for command execution and configuration.
      6
      -
    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

    A3.9/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct concern: topology file creation/layout/inspection/editing/validation/export versus device command/config/status/session operations. Potential overlaps like device_exec and device_push_config are clearly separated by purpose and usage.

    Naming Consistency4/5

    The topo_* and device_* prefixes create a strong overall pattern, and the verbs are consistent. list_models and environment_check break the prefix convention slightly, though their names are still clear and predictable.

    Tool Count4/5

    16 tools is slightly above the ideal range, but the count is justified by two clear subdomains: topology construction and device interaction. Every tool appears non-redundant and earns its place in the workflow.

    Completeness4/5

    The toolset covers the full topology lifecycle from creation to validation/export and pairs it with device command, config, query, and session management. Minor gaps like no explicit start/stop control or post-creation device setting update exist, but these fall outside the MCP's apparent scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources