Parallels 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_vmsB | List all Parallels Desktop virtual machines |
| get_vm_infoC | Get detailed information about a specific virtual machine |
| start_vmC | Start a virtual machine |
| stop_vmC | Stop a virtual machine |
| suspend_vmC | Suspend a virtual machine |
| resume_vmC | Resume a suspended virtual machine |
| reset_vmC | Reset (restart) a virtual machine |
| get_vm_statusC | Get the current status of a virtual machine |
| exec_vm_commandC | Execute a command inside a running virtual machine |
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 9 tools
Most tools have clearly distinct purposes: list, info, status, lifecycle controls, and command execution. The only mild overlap is between get_vm_info and get_vm_status, but the descriptions clarify detailed information versus current status.
All tool names follow a consistent snake_case verb_noun pattern, such as list_vms, get_vm_info, start_vm, and exec_vm_command. The convention is predictable throughout.
Nine tools are well-scoped for a VM management server, covering discovery, inspection, lifecycle control, and command execution without excessive overlap or missing core actions.
The set covers listing, status, start, stop, suspend, resume, reset, and command execution for existing VMs. However, creation, deletion, cloning, and snapshot operations are absent, leaving minor gaps for full VM lifecycle management.