io.github.AIops-tools/olvm-aiops
OfficialRelated Servers
Alternatives to io.github.AIops-tools/olvm-aiops
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides read-only Proxmox cluster oversight and configuration compliance checks through MCP, covering health, inventory, storage, backups, snapshots, and updates.-
- FlicenseNot gradedqualityAmaintenanceProvides authenticated read-only access to VMware Cloud Foundation Operations inventory, metrics, alerts, report definitions, targets, and skills via Streamable HTTP, with a durable audit trail and an admin UI.-

KVMFleet MCP Serverofficial
AlicenseAqualityDmaintenanceRead-only MCP server that allows AI assistants to query and monitor KVM Fleet devices, audit logs, and console sessions through the official REST API.59 npm1MIT- AlicenseBqualityCmaintenanceEnables read-only operational audits of schedulers, recurring job health, delivery failures, overdue runs, gateway/MCP health, and lock-file inventory without modifying inspected systems.11MIT
- FlicenseNot gradedqualityCmaintenanceEnables management of oVirt / Red Hat Virtualization environments via AI assistants, supporting VM lifecycle, power operations, snapshots, and infrastructure queries.-
- FlicenseAqualityCmaintenanceRead-only MCP server that exposes Kubernetes platform state (tenants, pods, SLOs, ArgoCD applications, chaos schedules, and catalog services) to AI agents, enabling natural language queries about cluster health and configuration.6-
TDQS
Scored across 17 tools
Every tool targets a distinct resource and action: list/get tools expose raw state, RCA tools provide ranked diagnosis for a specific entity type, and event/job/undo tools cover cross-cutting concerns. Even the four RCA tools are clearly separated by entity—engine, host, storage, VM—and their descriptions explicitly tell agents which one to use for which question.
All tool names follow a consistent lowercase snake_case `entity_action` pattern: `host_list`, `host_get`, `vm_stats`, `engine_health_rca`, `undo_apply`. The RCA variants all share the `_rca` suffix, and list/get pairs are uniform across hosts, storage domains, and VMs, making the naming scheme highly predictable.
At 17 tools, the count is slightly above the ideal sweet spot but justifiable given the server covers multiple entity types, raw inventory reads, per-entity diagnostics, events, jobs, stats, and undo bookkeeping. Each tool fills a clear role; only a few entity-specific get/list variations make it feel a bit heavy.
The toolset provides strong read and diagnostic coverage across the core oVirt/OLVM domains: data centers, clusters, hosts, storage, VMs, events, jobs, stats, and health RCA. Minor gaps exist—such as no detailed cluster/storage/VM health breakdowns beyond RCA and no broader write operations—but these are workarounds an agent can usually route around using existing tools.