Skip to main content
Glama

Related Servers

Alternatives to network-xray

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A read-only FastMCP server that enables AI assistants to query and retrieve network infrastructure information from NetBox using natural language.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for Cisco Meraki Dashboard, enabling LLMs to discover devices, check health, troubleshoot, and generate reports via natural language.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Read-only MCP server for NetBox that enables LLMs to query NetBox objects (devices, IPAM, etc.) and change logs through natural language, with field filtering for token optimization.
      4
      261
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server that exposes NetBox IPAM data over HTTP, allowing engineers to query subnets, IPs, and VLANs using natural language through AI assistants.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A read-only MCP server for interacting with Nautobot, enabling network source of truth queries, device management, IPAM, and data quality audits via tools and prompts.
      MIT

    TDQS

    B3.4/5.0

    Scored across 9 tools

    Disambiguation3/5

    Most tools target distinct resources, but why_best_path and why_path clearly overlap: why_path returns the selected path plus candidates, deciding step, and reason source, which subsumes why_best_path's 'best path plus reason' output. An agent can easily pick the wrong one of the pair. Additionally, lab_state, ospf_neighbors, and ospf_interfaces all lead with the same 'wrong' block, causing partial output overlap even though their primary payloads differ.

    Naming Consistency3/5

    All names are snake_case, which is good, and protocol-scoped tools (ospf_, bgp_) are consistently prefixed. However, the verb convention is mixed: list_routers and route_lookup lead with a verb, why_path and why_best_path use a why_ prefix, while lab_state, state_diff, ospf_neighbors, and ospf_interfaces carry no verb at all. The set is readable but not a predictable pattern.

    Tool Count5/5

    Nine tools is well-scoped for a read-only network lab diagnostic server. Each tool covers a distinct slice of the diagnostic surface (state summary, diffs, OSPF, BGP, routing table, path reasoning) without redundancy bloating the count.

    Completeness4/5

    The surface covers the core diagnostic workflow well: state snapshot, routers, OSPF neighbor/interface health with mismatch detection, BGP sessions, route lookup with longest-prefix match, path selection reasoning, and baseline diffing. Minor gaps exist, such as no dedicated LSDB inspection tool and no general BGP route-table listing (only per-prefix reasoning), but these are workable around.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues