
Parallels Desktop VMs
io.github.ParallelsPublished by GitHub account Parallelsv0.1.4Updated Oct 29, 2026
Control Parallels Desktop VMs from MCP: power, screenshot, exec, keyboard, sequences. macOS only.
Overview
Local macOS MCP server that lets an assistant find, start, inspect and control Parallels Desktop virtual machines, including guest commands and screenshots.
- What you can do
- List, search and inspect VMs, and start, resume, pause, suspend, stop, restart or reset them
- Run commands in Windows or Linux guests, including background jobs that can be monitored or cancelled
- Capture screenshots, read screen text with local OCR, and type text or send keys to the guest
- Create, list, switch and delete snapshots, clone VMs, and run multi-step tool sequences
- Change VM configuration, add, modify or remove devices, reclaim disk space, and manage VM encryption
- When to use it
- Useful when you work with Parallels Desktop on a Mac and want an assistant to check VM status, run commands inside a guest, read the guest screen, or automate repetitive VM setup and snapshot tasks.
- Requirements
- Runs locally on macOS with Parallels Desktop installed and an MCP client that launches the binary by absolute path. Guest command execution needs Parallels Tools in the guest; screen capture and keyboard tools need a running VM. Optional environment variables PDFM_MCP_VM_ID and PDFM_MCP_LOG_LEVEL, and launch arguments such as --read-only, --vm-id, --allow-vms, --allow-tools and --deny-tools.
Installation
In SourceWeft
- Open Parallels Desktop VMs in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Parallels Desktop MCP
[Join the pdfm-mcp community on Discord — join the server, then head to #pdfm-mcp]
Connect your AI assistant to Parallels Desktop. pdfm-mcp lets Claude, Codex, and other MCP clients find and manage your virtual machines, run guest commands, read the screen, and automate keyboard input.
Runs locally on macOS, with a universal binary for Apple Silicon and Intel. No Go or Node installation is needed to use the released binary.
What you can do
- Find a VM, check its status, and start or stop it.
- Run commands inside Windows or Linux guests and collect their output.
- Take screenshots, read screen text, and type into the guest.
- Create snapshots, clone VMs, and automate multi-step workflows.
Once connected, try asking your assistant: “Find my Ubuntu VM and show its status” or “Take a screenshot of my running Windows VM.”
Install
You need macOS, Parallels Desktop, and an MCP client. Guest command execution also requires Parallels Tools in the guest. Screen capture and keyboard tools need a running VM.
Homebrew and the default installer use stable releases. Until the first stable release and cask are published, use the script's prerelease option below. Check the Releases page for available builds.
Homebrew
Install script
The script verifies the release archive's SHA256 checksum and installs to /usr/local/bin. It asks for sudo only when the destination requires it.
To install the latest canary or beta:
For a particular version or a different directory, add --version <version> or --path <directory> after bash -s --.
Claude Desktop bundle
If the release includes pdfm-mcp-<version>.mcpb, download it and its matching .sha256 file from Releases. Verify it with shasum -a 256 -c pdfm-mcp-<version>.mcpb.sha256, then double-click the bundle to install. This is an alternative to configuring the binary manually below.
Connect your assistant
Your client starts the server for you. Use the binary's absolute path, since desktop apps may not inherit your terminal's PATH.
For Homebrew, "$(brew --prefix)/bin/pdfm-mcp" resolves the right path in terminal commands. In JSON or TOML configuration, use the actual path from the table; $(brew --prefix) is not expanded there.
Claude Code
Choose the command matching your installation:
Run claude mcp list to check the connection. These commands make the server available across your projects. See Claude Code's MCP setup for more options.
Codex CLI and IDE extension
Choose the command matching your installation:
Run codex mcp list to confirm registration, then use /mcp in the CLI to check active servers. The CLI and IDE extension share the same MCP configuration.
If you prefer editing ~/.codex/config.toml, add:
For the script installation or Intel Homebrew, change command to /usr/local/bin/pdfm-mcp. See the official Codex MCP documentation.
Plugin marketplaces
This repo is also a plugin marketplace for several assistants. Install the pdfm-mcp binary first and make sure it is on your PATH; the plugins only configure the client to launch it.
Cursor Teams and Enterprise admins can import this repository from Dashboard → Plugins & MCPs → Team Marketplaces.
Claude Desktop
Open ~/Library/Application Support/Claude/claude_desktop_config.json and add the server to mcpServers, preserving any existing entries:
This example uses Homebrew on Apple Silicon. For the script installation or Intel Homebrew, change command to /usr/local/bin/pdfm-mcp. Restart Claude Desktop after saving.
VS Code / GitHub Copilot
Add the server to .vscode/mcp.json in your project, preserving any existing servers:
For the script installation or Intel Homebrew, change command to /usr/local/bin/pdfm-mcp. Run MCP: List Servers from the Command Palette to start the server and check its status. See VS Code's MCP setup.
Available tools
By default, your assistant can work with all local VMs. Tools that target a VM accept its UUID or exact name. To restrict the server to one VM, add --vm-id "My VM" to its launch arguments.
See the tool reference for arguments, limits, and automation examples.
Choose what your assistant can access
Add launch arguments to limit access:
--read-only: expose observation tools for inspecting VMs and their screens.--vm-id "My VM": target one VM.--allow-vms "My VM,Another VM": restrict access to selected VMs.--allow-tools/--deny-tools: expose or hide specific tools.
For example, add "args": ["--read-only", "--vm-id", "My VM"] beside command in a JSON client configuration. In Codex TOML, use args = ["--read-only", "--vm-id", "My VM"].
Screenshots, recognized text, command output, and tool arguments reach your MCP client and its model provider. VM deletion, snapshot rollback, guest commands, and encryption can change or destroy data; review those actions before approving them.
Release builds can collect anonymised tool usage telemetry. To opt out, set PDFM_MCP_TELEMETRY_DISABLED=true in your server's environment. See configuration and privacy for all settings.
Update or uninstall
With Homebrew:
With the install script:
Add --pre-release when updating a canary or beta installation, or --path <directory> if you installed to a custom directory. Remove the server from your client's MCP settings after uninstalling.
Help and contributing
Join Discord and open #pdfm-mcp, or report an issue.
To build, test, debug, or add tools, see CONTRIBUTING.md.
Source: README.md at commit fc8bcd8
Tools
0Version history
4- v0.1.4LatestOct 15, 2026
- v0.1.3Oct 14, 2026
- v0.1.2Oct 13, 2026
- v0.1.1Oct 12, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts