io.github.AIops-tools/olvm-aiops
OfficialRelated Servers
Alternatives to io.github.AIops-tools/olvm-aiops
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to read Oracle Linux Virtualization Manager and oVirt inventory through the engine REST API, including VMs, hosts, and related details. It provides read-only tools for searching and retrieving VMs and KVM hosts.3Apache 2.0
- 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.52 npm1MIT- AlicenseBqualityAmaintenanceRead-only MCP server that exposes governed operational records with provenance and validity windows so clients can check which evidence is still current before answering. It lets agents reconcile freshness, schedule state, and evidence specificity to determine whether scheduled automations are actually healthy, rather than trusting an expired dashboard summary.4MIT
- 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
TDQS
Scored across 17 tools
List/get tools and the *_rca diagnostic tools are clearly separated, with explicit guidance in host_list and engine_health_rca pointing users to the RCA tool for 'what is wrong'. The four diagnostic aggregators (host, engine, storage, vm) have distinct scopes, though host_health_rca discussing VM candidates and vm_health_rca referencing storage creates minor cross-over.
Names follow a predictable resource_action snake_case pattern (host_list, vm_get, storage_domain_get, undo_apply). Verb choices vary (list, get, stats, health_rca, capacity_rca, apply) but the resource-first convention is consistent and readable throughout.
17 tools is reasonable for a platform spanning hosts, VMs, storage, datacenters, clusters, events, jobs plus diagnostics. Each tool maps to a distinct resource or diagnostic concern with little redundancy.
Read and diagnostic coverage is strong, but the surface is almost entirely read-only with no VM lifecycle, host maintenance, or other action tools, even though the undo framework implies write tools that generated the tokens but are not exposed here. Some resources also lack a get counterpart (cluster, datacenter, job).