Skip to main content
Glama
AIops-tools

fabric-aiops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to fabric-aiops

No user-submitted related servers found.

    Related Servers

    • firewall-aiops

      AIops-tools
      A
      license
      A
      quality
      A
      maintenance
      Governed OPNsense + pfSense firewall operations — gateway-health, rule-shadow, and blocked-traffic RCA, with guarded rule/alias writes, unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      35
      1
      MIT

    • rustunifimcp

      mechubsec
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a curated, scoped, audited MCP surface for managing UniFi Network controllers, offering typed read primitives, stats queries, scoped operational and backup actions, and multi-controller inventories. Change control uses a two-person approval lifecycle with pre-image capture, local validation, and best-effort rollback, since the controller has no candidate configuration or commit step.
      1
      MIT

    • proxy-aiops

      AIops-tools
      A
      license
      A
      quality
      A
      maintenance
      Governed reverse-proxy operations for Traefik, Caddy, and HAProxy — backend-health, cert-expiry, 5xx, and route-conflict RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      28
      MIT

    • Meraki MCP

      merakimiles
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides dynamic access to 400+ Meraki Dashboard API endpoints with intelligent discovery, plus advanced compliance auditing (PCI DSS, HIPAA, SOC2, ISO 27001, NIST), backup/restore operations, and network security analysis. Enables natural language queries to manage Meraki networks without pre-defined tools.
      4
      -

    • NetWarden

      danielshaji1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to discover, configure, harden, and troubleshoot multi-brand home and homelab networks through MCP, backed by declarative Terraform/OpenTofu orchestration. Includes safety guardrails, drift detection, snapshots, rollback, and zero-trust device controls.
      MIT

    • observability-aiops

      AIops-tools
      A
      license
      A
      quality
      A
      maintenance
      Governed Prometheus + Grafana operations — firing-alert and scrape-target RCA, alert noise/flapping analysis, silences, and dashboards, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      39
      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.6/5.0

    Scored across 37 tools

    Disambiguation4/5

    Most tools target a clearly distinct resource+action (client_get vs client_usage vs client_connectivity, aci_endpoint_trace vs aci_epg_segment, bind/unbind, claim/remove). The main overlap risk is among the health/summary reads — overview, org_device_statuses, device_status, network_health_score, and network_alerts all touch fleet/device health — but descriptions differentiate live rollups from single-entity reads from pure analysis. Only a few boundary pairs could occasionally be confused.

    Naming Consistency3/5

    All names are snake_case, but conventions are mixed: read tools are noun-first (org_list, network_vlans, client_get, device_uplinks) while write tools are verb-first (reboot_device, update_device, claim_devices_into_network). Within a single prefix the second token also flips between verbs and nouns (org_list/org_get vs org_licensing/org_admins). Readable, but not one predictable pattern.

    Tool Count3/5

    37 tools is heavy and sits above the comfortable 3-15 band, but the surface spans two distinct platforms (Meraki org/network/device/client/switch/wireless plus ACI fabric), three pure-analysis tools, and a governed write/undo layer, so most tools earn their place. It is borderline-heavy rather than padded.

    Completeness4/5

    Read coverage is broad and coherent (org, network, device, client, switch, wireless, ACI endpoints/EPGs/faults), writes cover the main remediation actions with undo tokens, and undo_list/undo_apply close the write loop. Gaps are minor: no network create/delete, no VLAN/SSID/switch-port creation or full config write, and ACI is read-only — workable but not full lifecycle.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources