Parallels Pro MCP Server
Related Servers
Alternatives to Parallels Pro MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server for managing Parallels Desktop VMs, including lifecycle operations and snapshots.-
- AlicenseBqualityCmaintenanceA stdio MCP server that controls VMware Workstation via vmrun, enabling VM lifecycle management and snapshot operations.14MIT
- AlicenseBqualityDmaintenanceAn MCP server that enables managing Parallels Desktop virtual machines, including listing, starting, stopping, suspending, and executing commands inside VMs.9MIT
- AlicenseNot gradedqualityBmaintenanceFirst-party MCP server and CLI for Xcode and iOS Simulator automation. Enables control of Xcode and iOS Simulator via MCP tools for tasks like building, testing, and automation.8 npm1MIT
- AlicenseAqualityBmaintenanceA local MCP server that exposes macOS automation actions (AppleScript + CLIs) as tools, enabling MCP clients on your Mac to control apps, system settings, and more.39MIT
- AlicenseAqualityBmaintenanceEnables MCP-compatible clients like Claude Desktop, Claude Code, Codex, and local-model hosts to inspect Proxmox VE clusters, nodes, VMs, containers, storage, snapshots, and tasks, with opt-in write operations for starting, stopping, cloning, backing up, and migrating guests. Read-only by default, it supports both stdio and Streamable HTTP transports.14MIT
TDQS
Scored across 24 tools
Tools are largely distinct — lifecycle, snapshot, file-transfer, and input tools each target a specific action. vm_list and vm_status both surface VM information (all vs. one), and vm_doctor vs. vm_optimize_windows both occupy 'maintenance' territory, creating minor selection ambiguity, but descriptions are clear enough to prevent real misselection.
The dominant pattern is object_verb snake_case (vm_start, vm_stop, snapshot_create), which is predictable within each namespace. However, snapshot operations use a snapshot_* prefix instead of the expected vm_snapshot_* style, and vm_changelog is a meta-tool about the server itself that breaks the VM-domain naming entirely.
At 24 tools, the set is on the heavy side, falling in the 16-25 borderline band. Most tools earn their place in a full VM management suite, but vm_changelog is a self-referential filler that doesn't belong, pushing an already large surface slightly beyond its scope.
The surface covers the full VM lifecycle (list/start/stop/suspend/delete/clone), complete snapshot CRUD, bidirectional file transfer, shared folder management, guest execution/input, and key configuration. Obvious gaps — no create-VM-from-installer, no restart/reboot, no rename or resource controls — are workaroundable (stop+start) but will force agents to improvise.