Skip to main content
Glama
Sign In
eiuemura

network-lab

by eiuemura
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to network-lab

No user-submitted related servers found.

    Related Servers

    • Network Lab MCP by CiscoDevNet

      Network Lab MCPofficial

      CiscoDevNet
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-capable AI clients to inspect live lab topology, manage terminal sessions, run commands, collect evidence, and support network investigation, troubleshooting, and validation while engineers retain control over managed definitions and decisions.
      7
      Apache 2.0

    • network-mcp

      E-Conners-Lab
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides AI assistants with direct access to multi-vendor network devices for tasks like configuration management, health checks, and topology discovery through 35 specialized tools. It enables natural language control over platforms including Cisco, Juniper, and Nokia using SSH, NETCONF, and SNMP protocols.
      12
      MIT

    • gnmi-mcp-server

      Howthemeaning
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage network devices via gNMI protocol, including querying capabilities, reading/modifying configurations, and subscribing to telemetry data through natural language.
      -
    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

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: two retrieve context (topology, instructions) and five handle terminal session lifecycle (open, send, read, list, close). There is no overlap or ambiguity between any of them.

    Naming Consistency5/5

    Tool names follow a consistent snake_case convention with a clear pattern: `get_*` for information retrieval and `terminal_*` for terminal operations. This makes the naming predictable and easy to navigate.

    Tool Count5/5

    With 7 tools, the server is well-scoped for its purpose: two context-gathering tools and five terminal management tools cover the necessary actions without unnecessary bloat or gaps.

    Completeness5/5

    The terminal session lifecycle is fully covered: open, send, read, list, and close. The topology and instructions tools provide sufficient context for the agent to operate. No obvious missing operations exist for the stated domain.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources