olvm-aiops
OfficialRelated Servers
Alternatives to 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 gradedqualityDmaintenanceProvides 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.-
- AlicenseBqualityBmaintenanceEnables read-only visibility into management status, assets, alerts, events, policies, reports, roles, users, and syslog through governed MCP and CLI calls. Credentials stay in environment variables, TLS verification remains on, and each call records a local audit event.35MIT

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.513 npm1MIT- AlicenseBqualityBmaintenanceRead-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
TDQS
Scored across 18 tools
Each tool targets a distinct resource+action, and the descriptions actively steer the agent away from overlap (host_list explicitly says to use host_health_rca for 'what is wrong with my hosts'; the four *_rca tools are scoped to disjoint signal sources — engine-only events, host-named events, VM-named events, storage-domain findings). Lists vs. get vs. stats vs. capacity-summary vs. RCA are cleanly separated, and undo_list/undo_apply are unambiguous.
Uniform snake_case with a resource-first, action-last pattern throughout: <resource>_list, <resource>_get, <resource>_health_rca, <resource>_capacity_rca, undo_apply. The only variation (storage_capacity_rca vs. storage_domain_list) is a resource qualifier, not a convention break, and it stays readable.
18 tools is slightly above the ideal 3-15 band, but each earns its place across four inventory domains plus one diagnostic and one control path; there is no filler. It reads as reasonable-but-heavy rather than bloated.
Read/observability coverage is thorough — datacenter, cluster, host, VM, storage domain, events, jobs, capacity, and per-domain RCA — with undo providing a reversal path for writes made elsewhere. The obvious gap is direct remediation (no vm_start/migrate, host_activate/maintenance, storage operations), so agents can diagnose but must act through tools outside this set.