Skip to main content
Glama
yeahdongcn

VMware Fusion MCP Server

by yeahdongcn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Related Servers

Alternatives to VMware Fusion MCP Server

No user-submitted related servers found.

    Related Servers

    • vmware-mcp

      havu0
      A
      license
      B
      quality
      D
      maintenance
      MCP server for controlling VMware Fusion/Workstation virtual machines via vmrun CLI, providing 32 tools for VM lifecycle, guest execution, and file operations without requiring a REST API daemon.
      32
      30 npm
      3
      MIT

    • Nutanix MCP Server

      atalhens
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server for Nutanix Virtual Machine Management APIs, enabling users to manage VMs, images, alerts, and logs via natural language through a CLI chatbot or any MCP client.
      -

    • 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

    • hcloud-mcp

      Xodus-CO
      A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server for the Hetzner Cloud API that enables natural language management of cloud infrastructure. Users can list, create, and modify servers, networks, volumes, and load balancers through MCP-compatible clients.
      67
      36 npm
      MIT

    • OpenAPI MCP Server

      rahgadda
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol Server that enables LLMs to interact with and execute REST API calls through natural language prompts, supporting GET/PUT/POST/PATCH operations on configured APIs.
      318 PyPI
      6
      Apache 2.0
    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.5/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: get_vm_info retrieves detailed VM data, get_vm_power_state focuses only on power status, list_vms enumerates all VMs, and power_vm performs power operations. There is no overlap or ambiguity between these functions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with snake_case: get_vm_info, get_vm_power_state, list_vms, and power_vm. The naming is predictable and uniform throughout the set.

    Tool Count4/5

    With 4 tools, the count is reasonable for basic VM management, covering listing, info retrieval, power state checks, and power actions. It might be slightly thin for advanced operations like configuration changes, but it's well-scoped for core functionality.

    Completeness3/5

    The tools cover core VM operations (list, info, power state, power actions), but there are notable gaps for a full VM management domain, such as creating/deleting VMs, modifying settings, or handling snapshots. Agents can perform basic tasks but may hit dead ends for more complex workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources