vmware-fusion-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VMRUN_PATH | No | Custom path to the vmrun binary if VMware Fusion is installed in a non-standard location. | /Applications/VMware Fusion.app/Contents/Library/vmrun |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fusion_list_runningA | List all currently running VMware Fusion virtual machines. Returns the count and paths of all running VMs, along with their display names. Returns:
Note: Only VMs started by the current user are shown (use sudo for root-started VMs). |
| fusion_list_allA | Discover all VMware Fusion virtual machines on the system by scanning common VM directories. Scans ~/Virtual Machines.localized and related paths for .vmx files. Also accepts an optional extra directory to search. Args:
Returns:
|
| fusion_get_vm_infoA | Get detailed information about a specific VMware Fusion virtual machine. Reads the .vmx configuration file and checks running status. Args:
Returns: Object with name, vmxPath, guestOS, memoryMB, numCPUs, annotation, hardwareVersion, running status. |
| fusion_start_vmA | Start (power on) a VMware Fusion virtual machine. Args:
Returns: Confirmation message on success. |
| fusion_stop_vmA | Stop (power off) a VMware Fusion virtual machine. Args:
Returns: Confirmation message on success. |
| fusion_suspend_vmA | Suspend a running VMware Fusion virtual machine. Saves the VM's state to disk. Args:
Returns: Confirmation message on success. |
| fusion_reset_vmB | Reset (reboot) a VMware Fusion virtual machine. Args:
Returns: Confirmation message on success. |
| fusion_get_ipA | Get the IP address of a running VMware Fusion guest OS. The VM must be running and have VMware Tools installed for this to work. Args:
Returns: The IP address as a string, or an error if unavailable. |
| fusion_list_snapshotsA | List all snapshots of a VMware Fusion virtual machine. Args:
Returns:
|
| fusion_create_snapshotB | Create a new snapshot of a VMware Fusion virtual machine. Args:
Returns: Confirmation message on success. |
| fusion_revert_snapshotA | Revert a VMware Fusion virtual machine to a previous snapshot. WARNING: This discards any changes made since the snapshot was taken. Args:
Returns: Confirmation message on success. |
| fusion_delete_snapshotA | Delete a snapshot from a VMware Fusion virtual machine. WARNING: This permanently removes the snapshot and its state. This cannot be undone. Args:
Returns: Confirmation message on success. |
| fusion_check_toolsB | Check the status of VMware Tools in a virtual machine's guest OS. Args:
Returns: The VMware Tools status (e.g., "installed", "running", "not installed"). |
| fusion_run_in_guestA | Run a program inside a VMware Fusion guest OS. Requires VMware Tools to be installed and running in the guest. Args:
Returns: Output from the program or confirmation that it was launched. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 14 tools
Most tools have clearly distinct purposes, but `fusion_list_running` and `fusion_list_all` both 'list' VMs which could cause initial confusion; descriptions clarify the scope difference. Snapshot, lifecycle, and guest operations are unambiguous.
All tools follow the `fusion_<verb>_<object>` pattern (e.g., `create_snapshot`, `start_vm`, `get_ip`). Even `list_running` and `list_all` fit the pattern with a gerund/adjective as the object, maintaining consistency across the set.
14 tools is well-scoped for a VMware Fusion control server, covering VM lifecycle, snapshots, guest operations, and discovery. Each tool serves a distinct purpose with no obvious redundancy or bloat.
The tool set adequately covers common VM management tasks: start/stop/suspend/reset, snapshot CRUD, guest program execution, and info retrieval. Missing operations like VM creation/deletion are reasonable omissions for a control-focused server, but could be considered minor gaps for a full lifecycle.