Desktop Hypervisor MCP server
io.github.bryanjbelanger/desktop-hypervisor-mcp·v2.1.2VirtualBox and VMware Fusion/Workstation behind one provider-neutral MCP tool surface.
0 stars
Reviews
Write oneNobody has reviewed Desktop Hypervisor yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Desktop Hypervisor tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 79 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Desktop Hypervisor compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 65/100
- higher than 20% of 48,255 servers
Install Desktop Hypervisor in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Desktop Hypervisor repository's README, as published. We do not edit it. Read it on GitHub
Desktop Hypervisor MCP
One provider-neutral MCP server for the desktop hypervisors: VirtualBox, VMware Fusion, and VMware Workstation. Nine tools, ~1,800 context tokens, full coverage of what its two predecessor servers did in ~5,600.
It succeeds virtualbox-mcp-server (that history is preserved on the predecessor-virtualbox branch) and the never- released vmware-fusion-mcp-server, folding both into one capability-based surface.
Versioning note: stable releases of this server start at v2.0.0. The v1.x line (and its v1.0.0 release, kept for anyone still pinning it) belongs to the virtualbox-only predecessor; the 0.x tags were this server's pre-stable iterations. v2.0.0 is identical in content to v0.4.3, re-versioned as the stable line.
Design
what they can actually do (provider action=list): guest exec, OVA import/export, linked clones, pre-boot guestinfo injection, DHCP-lease IP discovery, ISO mastering… Unsupported operations fail by naming the missing capability, not with a provider error.
- Capability-based, not lowest-common-denominator. Providers advertise
host can reach" is expressible on both families; "create a host-only interface" is not. The neutral tools express intent; provider-native mechanism stays reachable, unabstracted, through execute_command.
- Intent, not mechanism. "Ensure the cluster nodes share a network the
hypervisor the artifact it can actually import — Talos's vmware-.ova vs virtualbox-.ova, Vagrant's vmware_desktop vs virtualbox boxes, Microsoft's per-hypervisor dev VM — keyed on (image, provider family, host arch).
- Artifacts resolve per provider. The same image name gives each
Tools
With one hypervisor installed it is selected automatically; with several, the ambiguity is surfaced, never guessed.
Image catalog
artifact action=catalog lists maintained images: Talos (appliance and metal ISO), Ubuntu (cloud image and Vagrant), Debian, Fedora, Rocky, Alma, openSUSE, FreeBSD, Kali, TurnKey, the Windows dev VM, plus vagrant:org/box passthrough to the whole registry. Downloads are sha256-verified wherever the publisher provides a digest (GitHub release assets always do); unverified sources say so loudly. Vagrant boxes are fetched for the right provider and auto-extracted to their importable machine file. The cache lives in ~/.hypervisor-images (HVIMAGEDIR overrides).
Prerequisites
Detection is per-call, so a hypervisor installed mid-session is picked up.
- VirtualBox (VBoxManage) and/or VMware Fusion / Workstation (vmrun).
- Nothing else: a single static Go binary, no Python, no Node.
Optional, detected at runtime: ovftool enables OVA import/export on VMware; xorriso enables repack_iso.
Installing
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Desktop Hypervisor: common questions
- Is Desktop Hypervisor MCP server safe?
- With care: it is graded C, so read the findings first (65/100). Read the Desktop Hypervisor safety report
- Does Desktop Hypervisor need an API key?
- Yes. The registry entry asks for
HV_GUEST_PASSWORD. - Is Desktop Hypervisor maintained?
- The last commit was 80 days ago (2026-08-16). The latest release is v2.1.2.