Skip to main content
Glama

Related Servers

Alternatives to ENSP-MCP AI

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      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.
      -
    • 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
      1
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables large language models to manage network devices (Cisco, Huawei, H3C, Ruijie) via Telnet/SSH, supporting command execution, configuration, and diagnostics.
      15
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI-powered network engineering by providing natural language control over GNS3 network simulations. Supports creating projects, building network topologies, managing devices, controlling simulations, and analyzing network traffic through conversational AI interactions.
      42
      27
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to interact with local H3C Cloud Lab network simulation environments, allowing discovery of projects, devices, and links, as well as execution of Comware CLI commands.
      1
      Apache 2.0

    TDQS

    B3.1/5.0

    Scored across 20 tools

    Disambiguation2/5

    Several tools are near-duplicates with only subtle target differences: execute_cli vs mcp_execute, push_config vs mcp_push_config, and health_check vs mcp_health_check. Topology tools such as discover_topology, find_topo_files, get_topology_context, and sync_topology_devices also overlap enough that an agent could easily choose the wrong one.

    Naming Consistency3/5

    Most tools use snake_case verb_noun naming, but the set mixes plain names with mcp_ and multi_ prefixes, and health_check is noun-first rather than verb-first. The pattern is readable but not fully predictable across the whole server.

    Tool Count3/5

    20 tools is on the heavy side for an eNSP device-management server, especially because several mcp_ variants duplicate their base counterparts. The scope is plausible, but the surface feels somewhat inflated by redundant topology-synced-device versions.

    Completeness4/5

    Core workflows are covered: device registration, discovery, CLI execution, configuration push/save, connectivity checks, and topology synchronization/context. Minor gaps remain, such as device metadata updates, broader batch CLI execution, topology editing, and explicit rollback support.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues