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
      B
      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
      -

    • nautobot-mcp

      reshif
      A
      license
      Not graded
      quality
      B
      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

    • NetBox MCP Server

      mhajder
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to read and manage NetBox network infrastructure data via MCP. Supports querying all object types, search, changelogs, GraphQL, IP/prefix/VLAN allocation, cable tracing, config rendering, and write operations with safety modes.
      18
      203 PyPI
      1
      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 33 tools

    Disambiguation5/5

    Each tool has a unique purpose with no overlap. For example, get_bgp_neighbors and get_bgp_neighbors_detail differ by detail level, and get_interfaces, get_interfaces_counters, get_interfaces_ip are all distinct. Config operations (backup, diff, merge, replace) are clearly separated, and RCA tools address specific issues.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with lowercase and underscores (e.g., get_lldp_neighbors, config_backup, netbox_list_devices). The naming is predictable and readable, with no mixing of styles.

    Tool Count4/5

    33 tools is slightly high but justified for the breadth of network AIOps: monitoring, configuration, NetBox integration, and troubleshooting. Each tool addresses a specific need, though some consolidation might be possible.

    Completeness4/5

    The tool set covers read operations for many network aspects, configuration management with rollback/revert, NetBox source-of-truth, and RCA. Missing direct write tools for specific protocols, but config merge/replace covers generic changes. Minor gaps exist but core workflows are complete.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources