Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Desktop Hypervisor MCP
Overview
Description from the maker (original English)
VirtualBox and VMware Fusion/Workstation behind one provider-neutral MCP tool surface.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
- You need to fill in: HV_GUEST_PASSWORD
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
HV_GUEST_USER,HV_GUEST_PASSWORD,HV_IMAGE_DIR
Values marked secret are keys to your account. Never share them or paste them into a chat.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
HV_GUEST_USERenvUsername for in-guest operations (exec, script, file copy). Omit if guest operations are not needed.- Password for in-guest operations. Read from the server environment, never accepted as a tool parameter.
HV_IMAGE_DIRenvCache directory for downloaded OS images. Defaults to ~/.hypervisor-images.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account bryanjbelanger, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32680 servers in this category
- Published to the registry more recently than 24% of the other 32680 servers in this category
- Basic checks equal to or better than 100% of the other 32680 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Desktop Hypervisor MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: HV_GUEST_PASSWORD
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (2.1.2) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated 2 days ago
Install
EmbeddedCI BenchPod
by embeddedci-com
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
Runs on your computerUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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
- Capability-based, not lowest-common-denominator. Providers advertise 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. - Intent, not mechanism. "Ensure the cluster nodes share a network the 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. - Artifacts resolve per provider. The same image name gives each hypervisor the artifact it can actually import — Talos's
vmware-*.ovavsvirtualbox-*.ova, Vagrant'svmware_desktopvsvirtualboxboxes, Microsoft's per-hypervisor dev VM — keyed on (image, provider family, host arch).
Tools
| Tool | Actions |
|---|---|
provider | list — installed hypervisors with status, capabilities, formats, and remediation when not ready |
artifact | catalog, resolve, fetch (dry_run) — verified downloads of official OS images, per provider |
vm_lifecycle | create, start, stop, suspend, reset, delete, clone, import, export |
vm_info | list, running, show, ip (in-guest tools, else DHCP leases by MAC — works for agentless guests like Talos) |
vm_config | resources, nested_virt, attach_iso, guestinfo (pre-boot key/value injection, VMware) |
snapshot | take, restore, delete, list (tree) |
guest | exec, script, copy_in, copy_out, screenshot |
network | ensure_cluster_network, expose_guest_port, make_iso, repack_iso |
execute_command | raw VBoxManage / vmrun argv on the selected provider |
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 (HV_IMAGE_DIR overrides).
Prerequisites
- VirtualBox (
VBoxManage) and/or VMware Fusion / Workstation (vmrun). Detection is per-call, so a hypervisor installed mid-session is picked up. - 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
Published on the official MCP Registry as io.github.bryanjbelanger/desktop-hypervisor-mcp — that name is what registry-aware clients install by. The registry has no per-server page yet, so the listing itself is the API record: current entry.
For hosts that support MCP Bundles, download the .mcpb from the latest release and open it — guest credentials and the image cache directory are prompted for in the host's own UI. One bundle covers every platform; it carries a binary per (os, arch) and picks one at startup, so it is ~16 MB.
Otherwise take the bare binary for your platform from the same release, or build it:
go build -o desktop-hypervisor-mcp .Registration with Claude Code
claude mcp add --scope user hypervisor -- /path/to/desktop-hypervisor-mcpGuest-operation credentials come from the server environment, never from tool parameters:
claude mcp add --scope user hypervisor \--env HV_GUEST_USER=vagrant --env HV_GUEST_PASSWORD=vagrant \ -- /path/to/desktop-hypervisor-mcp
(VMRUN_GUEST_USER/VMRUN_GUEST_PASSWORD are honored for compatibility.)
The server ships usage recipes in the MCP initialize handshake, generated from what was actually detected on the host — a session on a VirtualBox-only machine never pays context for VMware guidance.
Permissions
Per-tool allowlisting in .claude/settings.json keeps prompts meaningful — read-only tools are safe to always-allow:
{"permissions": { "allow": [ "mcphypervisorprovider", "mcphypervisorvm_info", "mcphypervisorartifact", "mcphypervisorsnapshot" ] } }
Keep mutating tools (vm_lifecycle, execute_command) behind prompts unless you accept unattended VM mutation.
Bundled skills
skills/ contains workflow skills for Claude Code — procedures that compose this server's tools across either hypervisor: hv-vm (provisioning), hv-network (networks, guest reachability, seed ISOs), hv-snapshot (safety workflows), hv-maintenance (inventory & cleanup), hv-transfer (clone/export/move). Install by copying (or symlinking) into ~/.claude/skills/. They supersede the predecessor's vbox-* skills.
Related projects
- talos-mcp-server — Talos/Kubernetes orchestration; consumes this server for node provisioning and stays deliberately hypervisor-agnostic.