VMware Fusion MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_vmsB | List all VMs in VMware Fusion. |
| get_vm_infoB | Get detailed information about a specific VM. |
| power_vmA | Perform a power action on a VM. Valid actions are 'on', 'off', 'shutdown', 'suspend', 'pause', 'unpause'. |
| get_vm_power_stateB | Get the power state of a specific VM. |
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 4 tools
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.
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.
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.
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.