Skip to main content
Glama
ShubhaKul

olvm-mcp

by ShubhaKul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to olvm-mcp

No user-submitted related servers found.

    Related Servers

    • oVirt MCP Server

      puhamihai
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables management of oVirt / Red Hat Virtualization environments via AI assistants, supporting VM lifecycle, power operations, snapshots, and infrastructure queries.
      -
    • io.github.AIops-tools/olvm-aiops by AIops-tools

      io.github.AIops-tools/olvmofficial

      AIops-tools
      A
      license
      A
      quality
      A
      maintenance
      Provides read-only, governance-audited operations for OLVM and oVirt 4.5 engines, enabling inventory, health, capacity, and diagnosis queries over MCP and CLI with audit logging and budget guards.
      17
      MIT

    • Proxmox MCP Server

      teomarcdhio
      A
      license
      A
      quality
      D
      maintenance
      Enables read-only interaction with Proxmox homelab VMs and containers, allowing LLM agents to list VMs, monitor status and performance metrics, view snapshots, and check cluster health through natural language queries.
      8
      MIT

    • openstack-mcp

      abhishekambad-leapswitch
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to inspect and manage OpenStack clouds, including listing instances, checking quotas, and retrieving console logs. It supports opt-in write operations for creating and deleting servers, with a read-only default.
      12
      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.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: list_vms and list_hosts enumerate different resources, and get_vm provides single-VM detail. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All three tools follow a consistent verb_noun pattern (list_vms, get_vm, list_hosts), with plural nouns for list operations and singular for the detail operation, which is idiomatic and predictable.

    Tool Count3/5

    Three tools is borderline thin for an oVirt virtualization server; it covers only basic VM and host inventory, leaving little room for the broader management surface the domain implies. A read-only inventory intent could justify this, but it feels underpowered.

    Completeness2/5

    The surface only supports listing VMs, getting one VM, and listing hosts. It lacks VM lifecycle actions (start/stop/reboot), host detail or operations, cluster and storage domain queries, and create/update/delete operations, which are significant gaps for an oVirt management server.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources