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
      B
      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
      C
      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.
      21
      -

    • 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 maps to a unique resource+action; same-resource operations are clearly separated (session_get/list vs session_logoff/disconnect/send_message, machine_list/get vs reset/maintenance/remove). The aggregate read tools also have distinct outputs, so there is no real risk of picking the wrong tool for a task.

    Naming Consistency4/5

    The set is mostly consistent and all snake_case, with resource-first names and predictable _get/_list suffixes. Some names break the pattern: machine_maintenance is not an imperative, and health_summary/session_stats/pool_utilization are noun phrases rather than action verbs.

    Tool Count4/5

    27 tools is on the high side of the ideal range, but the VDI domain is broad and each tool covers a distinct operation or read view across sessions, machines, pools, entitlements, tasks, farms, and apps. There is little redundancy, so the count feels justified rather than bloated.

    Completeness4/5

    Core operational workflows are well covered: read/list for every resource, high-risk write actions with confirm gates, task status/cancel, entitlements, and health reporting. Gaps exist at the lifecycle level (no pool create/update/delete, no app-pool or farm management beyond listing), but these are not fatal for the apparent operational purpose.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources