Skip to main content
Glama
Sign In
steinzi

netlab-mcp

by steinzi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to netlab-mcp

No user-submitted related servers found.

    Related Servers

    • PNETLab MCP Server

      omichelbraga
      A
      license
      A
      quality
      D
      maintenance
      Enables programmatic control of a PNETLab network-emulation lab via natural language, allowing users to build topologies, wire links, push device configs, and boot the lab through an LLM agent.
      31
      5
      Apache 2.0

    • Packet Tracer MCP

      Arminfx7
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables LLMs to plan, validate, generate, and deploy Cisco Packet Tracer network topologies from natural-language prompts, including routing, switching, DHCP, VLANs, security, IPv6, wireless, live deployment, verification, and .pkt project management.
      3
      MIT

    • network-lab

      eiuemura
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to understand lab topologies, follow operational principles, and interact with real network devices through observable terminals while keeping private access information hidden.
      7
      Apache 2.0

    • pyATS MCP Server

      sunayan22doli-bit
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to directly inspect, configure, test, and orchestrate network devices through pyATS/Genie, including show command parsing, config rollback, feature state learning/diffing, fleet-wide command fan-out, and declarative test execution.
      MIT

    • cml-mcp-server

      dr-stutters
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to explore, build, run, and troubleshoot Cisco Modeling Labs (CML 2.x) network topologies, including lab construction from specs, console command execution, reachability testing, packet capture analysis, link impairment scenarios, and topology diagram export.
      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

    A3.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: topology generation, known-good retrieval, host check, example listing, compatibility query, config rendering, failure reporting, and lab validation. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., generate_topology, validate_in_lab, report_failure). Naming is predictable and readable.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a netlab MCP server. Each tool is justified and covers a specific step in the workflow without being excessive or insufficient.

    Completeness5/5

    The tool surface covers the full lifecycle: topology generation, config rendering, validation, host readiness, compatibility queries, failure reporting, and example browsing. No obvious missing operations for the intended domain.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources