Skip to main content
Glama
AIops-tools

io.github.AIops-tools/network-aiops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to io.github.AIops-tools/network-aiops

No user-submitted related servers found.

    Related Servers

    • mcp-oxidized

      meks007
      F
      license
      A
      quality
      D
      maintenance
      Provides MCP tools to query, compare, and analyze network device configurations managed by Oxidized, such as listing devices, viewing backup status, and generating diffs between configuration versions.
      8
      -

    • TheBoringMCP_netbox

      theboringalex
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to create, read, update, and delete NetBox resources such as sites, networks, VLANs, IP addresses, devices, interfaces, cables, and VMs through generic CRUD and convenience tools, with automatic name/slug resolution and optional read-only or API-key protection.
      MIT

    • netdiag-mcp

      chaojiwudipaozi
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to drive switches, servers, and consoles over SSH or serial Console through 28 MCP tools, auto-detecting vendors, paging through long output, and cleaning raw byte streams into readable text. Provides structured diagnostics (interfaces, ARP/MAC/routing tables, ping, logs, health checks) plus a three-tier safety model with audit logging, credential redaction, and dry-run config changes.
      MIT

    • nautobot-mcp

      reshif
      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

    • juniper-junos-mcp

      anderson-jason573
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables safe interaction with Juniper Junos devices (SRX firewalls) via MCP, providing operational read tools and a configuration change flow with device-side diff preview and automated rollback.
      Apache 2.0
    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.5/5.0

    Scored across 33 tools

    Disambiguation3/5

    Several tool families overlap in purpose: get_bgp_neighbors vs get_bgp_neighbors_detail vs bgp_neighbor_rca, get_lldp_neighbors vs get_lldp_neighbors_detail, config_diff vs config_merge/replace dry_run, and device_health vs its underlying getters. Descriptions clarify the distinctions, but an agent still faces non-trivial choices among near-equivalent read/diagnostic tools.

    Naming Consistency4/5

    Names are all snake_case and mostly follow domain prefixes (get_, config_, netbox_, undo_, *_rca, device_). Minor deviations exist, such as device_facts/device_health lacking get_, and netbox_device_interfaces lacking a verb while netbox_list_devices and netbox_get_device include one.

    Tool Count2/5

    33 tools is high for a single MCP server and exceeds the 25-tool threshold where count becomes unwieldy. Though the network domain is broad, several tools are redundant variants of summary/detail or aggregate/raw operations, suggesting consolidation is possible.

    Completeness4/5

    The surface covers config lifecycle, wide read telemetry, targeted RCA, NetBox inventory, and undo tokens, which is strong for network AIOps. Gaps remain, including OSPF/ISIS neighbor state, an explicit ping/reachability test for safe commits, and a tool to list locally configured target devices.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources