Skip to main content
Glama
vmware-skills

vmware-vdi

by vmware-skills
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to vmware-vdi

No user-submitted related servers found.

    Related Servers

    • VMware_MCP_SERVER

      DanilenkA
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides AI agents with comprehensive access to VMware vSphere operations, including VM management, monitoring, and vSAN read-only monitoring, through a secure Docker environment.
      Apache 2.0

    • vSphere MCP Server

      giuliolibrando
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for VMware vSphere management, enabling AI agents to perform VM operations, monitoring, snapshots, and reporting through a secure, Dockerized environment.
      23
      -

    • Nutanix AIops

      AIops-tools
      A
      license
      A
      quality
      A
      maintenance
      Governed AI-ops MCP server for Nutanix Prism Central v4 REST API, offering 47 read/write tools for clusters, VMs, storage, network, catalog, data protection, alerts, and LCM upgrades with built-in audit, budget, and risk-tier governance.
      51
      MIT

    • vsphere-mcp

      fukui-yuto
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for VMware vSphere/vCenter operations, enabling natural language control of VMs, hosts, and infrastructure.
      Apache 2.0

    • nutanix-mcp

      NoBanks
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Nutanix Prism Central v4 REST API, enabling AI agents to list and inspect VMs, control VM power state, list clusters, read alerts, and list subnets.
      8
      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

    A4.2/5.0

    Scored across 27 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: lists vs single-gets are paired (list_desktop_pools/get_desktop_pool, list_vdi_machines/get_vdi_machine, list_vdi_sessions/get_vdi_session), write operations are unique verbs (reset, maintenance, remove, enable, push, logoff, disconnect, message), and the three reporting tools (health_summary, session_stats, utilization) are explicitly differentiated as aggregate vs per-row views. Descriptions even cross-reference ('the reporting counterpart to list_vdi_sessions'), leaving little room for misselection.

    Naming Consistency4/5

    Names follow a predictable snake_case verb_noun pattern (list_*, get_*, set_*, remove_*, add_*, cancel_*, search_*). Minor deviation: the 'vdi' domain token appears inconsistently (list_vdi_machines, list_vdi_sessions) while other resources drop it (list_desktop_pools, list_app_pools, list_farms).

    Tool Count4/5

    27 tools is on the heavy side, but each covers a genuinely distinct object (pools, farms, images, machines, sessions, entitlements, tasks, events) with no redundant duplicates. Slightly over the ideal band but justified by the broad VDI management surface.

    Completeness4/5

    Strong lifecycle coverage: pools (list/get/enable/push image), machines (list/get/reset/maintenance/remove), sessions (list/get/logoff/disconnect/message), entitlements (list/add/remove), plus tasks, events, and health/stats reporting. Gaps exist in provisioning (no desktop pool/farm creation or deletion, farms are read-only), which is acceptable for an operations-focused server but leaves some lifecycle dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources