Skip to main content
Glama
VMware-Monitor

VMware-Monitor

Related Servers

Alternatives to VMware-Monitor

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      AI-powered VMware vCenter/ESXi monitoring and operations. 20 MCP tools for inventory queries, health monitoring, VM lifecycle management, fast provisioning (Linked Clone, OVA, template deploy), snapshot management, and datastore browsing. Supports vSphere 6.5–8.0. Works with local models via Ollama/LM Studio.
      44
      398 PyPI
      87
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to manage VMware vSphere infrastructure through 55 typed tools built on the govc CLI. It supports comprehensive operations including VM lifecycle management, snapshot control, datastore navigation, and networking configuration.
      48 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives AI agents direct access to VMware vSphere infrastructure, enabling VM lifecycle management, snapshots, datastore operations, networking, and more via 55 typed tools built on govc.
      48 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage VMware vSphere virtual infrastructure through comprehensive operations including VM power control, snapshot management, resource monitoring, performance analytics, and bulk operations with built-in safety confirmations for destructive actions.
      -
    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server that lets Claude query a VMware vCenter environment through the vSphere REST API, listing virtual machines, ESXi hosts, clusters, datastores, networks, datacenters, resource pools, and folders. It issues only GET requests and can run over stdio or authenticated Streamable HTTP, so inventory questions can be answered without any risk of changing the environment.
      9
      MIT

    TDQS

    A4.2/5.0

    Scored across 33 tools

    Disambiguation4/5

    The suite uses a clear layered model (list/get/investigate/fleet rollup), and most descriptions explicitly route an agent between overlapping-looking tools. A few boundaries still require close reading, such as get_vm_info vs investigate_vm and get_events vs scan_host_logs, so not every tool is instantly distinguishable.

    Naming Consistency5/5

    Tool names consistently use snake_case with a predictable verb prefix: list_, get_, investigate_, find_, and scan_. The pattern is stable across all 33 tools and makes the intended action clear.

    Tool Count2/5

    At 33 tools, the server is well past the typical 3-15 range and includes many niche read-only endpoints such as vCenter deployment size, memory tiering, and vLCM apply results. While broad VMware monitoring can justify a large surface, this is heavy for one MCP server and increases cognitive load.

    Completeness4/5

    Coverage is broad across inventory, cluster health, performance, alarms/events, logs, hardware sensors, storage capacity, snapshots, licenses, certificates, NTP, access, and patch compliance. The main gaps are historical trending and some appliance-level details, but agents can work around these for most monitoring tasks.

    Maintenance

    ActivityActive
    ResponsivenessLimited data