Skip to main content
Glama

Related Servers

Alternatives to ensp-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to author Huawei eNSP topologies as .topo files and to read and drive the live console of any running device VM by capturing screenshots and injecting text or named keystrokes through VirtualBox. It also lists the device catalogue with interface index order, validates and opens topologies, and reports which eNSP devices and console channels are available.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables automation of Huawei eNSP lab workflows by generating topology files, starting and stopping devices through the eNSP GUI, and pushing VRP configuration one command at a time with per-command error reporting. It exposes 12 MCP tools and 23 scenario presets for managing network labs.
      3,432 npm
      68
      GPL 3.0
    • A
      license
      B
      quality
      C
      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
      2
      MIT
    • F
      license
      B
      quality
      C
      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.
      20
      10
      -
    • 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.
      35
      -

    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

    ActivityNo data
    ResponsivenessOutdated data