Skip to main content
Glama

Related Servers

Alternatives to xcpng-aiops

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      A
      maintenance
      Governed Docker + Portainer container-host operations (non-Kubernetes) — restart-loop, resource-pressure, and image/volume-bloat RCA, with guarded lifecycle writes, unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      38
      MIT
    • 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
    • A
      license
      A
      quality
      A
      maintenance
      Governed SSO/IAM operations for Keycloak and Authentik — login-failure, stale-permission, client-config, and MFA RCA, with unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      29
      MIT
    • 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
    • A
      license
      A
      quality
      A
      maintenance
      Governed MinIO object-storage operations — capacity, exposure-surface audit, lifecycle, and healing RCA, with guarded bucket writes, unbypassable audit logging (MCP + CLI), budget/runaway guards, dry-run, and undo/rollback.
      48
      MIT

    TDQS

    A3.9/5.0

    Scored across 29 tools

    Disambiguation5/5

    Every tool targets a distinct resource+action: list vs get pairs are clear, the four RCA tools (backup_failure_rca, pool_patch_ha_posture, sr_usage_rca, vm_health_rca) are differentiated by domain, and destructive pairs (snapshot_delete vs snapshot_revert, vm_stop vs vm_reboot) are cleanly separated. The aggregate overview tool is clearly marked as a fan-out, so it does not blur the granular reads.

    Naming Consistency5/5

    Consistent snake_case resource_action convention throughout (vm_list, vm_get, vm_start, host_list, sr_get, snapshot_create, undo_apply). The only deviations (overview, the *_rca tools) still follow the resource-first snake_case style and remain predictable.

    Tool Count3/5

    29 tools is above the comfortable range and pushes into 'heavy' territory for a single server. The breadth (pools, hosts, VMs, SRs, VDIs, snapshots, backups, tasks, undo) justifies much of it, but the surface is at the upper limit of what an agent can navigate reliably.

    Completeness3/5

    Snapshot lifecycle (create/delete/revert) and VM power lifecycle (start/stop/reboot/migrate) are well covered, and the undo system is a strong addition. However, there is no VM create/delete/clone, no host maintenance or pool provisioning actions, and backup tools are read-only, leaving notable gaps for real ops workflows.

    Maintenance

    ActivityActive
    ResponsivenessNo issues