Skip to main content
Glama
AIops-tools

fabric-aiops

by AIops-tools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

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

    • observability-aiops

      AIops-tools
      A
      license
      B
      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

    • cicd-aiops

      AIops-tools
      A
      license
      A
      quality
      A
      maintenance
      Governed CI/CD operations for self-hosted GitLab and Gitea — pipeline-failure, runner, artifact-bloat, and stale-branch RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      28
      MIT

    • Monitoring AIops

      AIops-tools
      A
      license
      A
      quality
      A
      maintenance
      Governs and automates network monitoring across SolarWinds Orion and Paessler PRTG platforms with a unified MCP server, enabling querying, alert management, and governed writes with audit logging.
      42
      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 34 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, targeting different resources (clients, devices, networks, org) or different aspects (list/get/usage/connectivity). Even overlapping terms like device_status vs org_device_statuses are differentiated by scope and description.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (e.g., client_get, device_inventory, reboot_device). However, some deviate (client_connectivity, network_health_score, uplink_loss_and_latency_rca) or use long phrases, but overall the naming is readable and predictable.

    Tool Count3/5

    34 tools is high for a typical MCP server, covering many read and write operations. While each tool has a distinct role, the sheer number may overwhelm agents. It is borderline but not extreme.

    Completeness2/5

    The tool set heavily favors read operations (20+ reads) with limited writes (reboot, blink, update device/VLAN, claim/remove, bind/unbind). Missing create/delete for networks and VLANs, write access for SSIDs, switch ports, or other common configuration tasks. Significant gaps hinder full lifecycle management.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources