R
rumenjordanov/vmware-sandbox-mcp
Give your AI agent a disposable computer.
★ 2·updated 2026-11-17
View on GitHub ↗Direct link · no redirect page
We have no copy-paste install command and no public remote endpoint, so we do not print a config. The step above is reference only, not a command we can vouch for. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 2 ★ · rumenjordanov/vmware-sandbox-mcp · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 2 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
rumenjordanov/vmware-sandbox-mcp;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# vmware-sandbox-mcp
Excerpted from the repository README (abridged)
Give your AI agent a disposable computer.
An MCP server that lets Claude and other AI agents create a real Linux virtual machine,
run anything in it, and throw it away. It runs on your own PC with VMware Workstation.
Quick start · Tools · Network modes · Security · Setup guide
A real sandbox: the agent logged in, opened the text editor and typed, using only the tools below.
## Why
You want an agent to run an install script from a forum, try an unknown package, or click through a desktop program. You do not want it doing that on your own machine.
A full virtual machine, not a container. Each sandbox is its own VM with its own kernel, created from a clean snapshot (about 25 seconds on the test machine) and deleted when the agent is done.
The agent never sees VMware. It gets 15 plain tools: create a computer, run a command, copy files, look at the screen, click, type, save a checkpoint and roll back to it, destroy. This is deliberately not a general VMware management server.
Your other VMs are off limits. The server can only touch virtual machines it created itself. That is enforced in code and covered by tests, not left to the agent's good behaviour.
Internet without your home network. In web mode a sandbox can download from public websites but cannot reach your PC, your router or anything else on your network.
Everything is logged. Every command, file copy, click and web request goes into an audit log the agent cannot read or change.
Local. No cloud account, no API key, no per-minute billing. It needs VMware Workstation and Python, nothing else.
## What you can ask for
> I found install.sh on a forum. Put it in a sandbox, run it with web access, and tell me what it actually does before I run it for real.
> Start a sandbox, install nginx, serve this folder with it and check that the page loads.
> Open the text editor in a sandbox, type a short note, save it, and show me a screenshot.
For the first one, the agent:
1. calls sandbox_create(network="web") and gets a sandbox_id back;
2. calls sandbox_copy_in to copy install.sh from your transfer folder into the sandbox;
3. calls sandbox_run to execute it, then again to inspect new files, processes and services;
4. calls sandbox_copy_out to save a report into your transfer folder;
5. calls sandbox_destroy. Whatever the script did is gone.
## How it works
mermaid
flowchart LR
A["AI agent (Claude)"] -- "MCP (stdio)" --> S["vmware-sandbox-mcp"]
S -- "clone from, never start" --> B[("base VM clean snapshot")]
S -- "allowlisted vmrun calls" --> C[("sandbox linked clone")]
C -- "web mode only" --> P["filtering proxy"]
P --> I(("public internet"))
S --- T["transfer folder"]
S --- L["audit log"]
Every sandbox is a linked clone of one powered-off snapshot of a Linux VM that you prepare once. Before a clone boots for the first time, its settings are rewritten: no shared folders, no clipboard, no USB, no CD-ROM, and no network unless the agent asked for one.
## Requirements
A Windows host with VMware Workstation Pro and its vmrun command-line tool. Developed and tested on Workstation 25H2 (vmrun 1.17.0) on Windows 11. Linux hosts are not supported.
Python 3.11 or newer.
An MCP server that lets Claude and other AI agents create a real Linux virtual machine,
run anything in it, and throw it away. It runs on your own PC with VMware Workstation.
Quick start · Tools · Network modes · Security · Setup guide
A real sandbox: the agent logged in, opened the text editor and typed, using only the tools below.
## Why
You want an agent to run an install script from a forum, try an unknown package, or click through a desktop program. You do not want it doing that on your own machine.
A full virtual machine, not a container. Each sandbox is its own VM with its own kernel, created from a clean snapshot (about 25 seconds on the test machine) and deleted when the agent is done.
The agent never sees VMware. It gets 15 plain tools: create a computer, run a command, copy files, look at the screen, click, type, save a checkpoint and roll back to it, destroy. This is deliberately not a general VMware management server.
Your other VMs are off limits. The server can only touch virtual machines it created itself. That is enforced in code and covered by tests, not left to the agent's good behaviour.
Internet without your home network. In web mode a sandbox can download from public websites but cannot reach your PC, your router or anything else on your network.
Everything is logged. Every command, file copy, click and web request goes into an audit log the agent cannot read or change.
Local. No cloud account, no API key, no per-minute billing. It needs VMware Workstation and Python, nothing else.
## What you can ask for
> I found install.sh on a forum. Put it in a sandbox, run it with web access, and tell me what it actually does before I run it for real.
> Start a sandbox, install nginx, serve this folder with it and check that the page loads.
> Open the text editor in a sandbox, type a short note, save it, and show me a screenshot.
For the first one, the agent:
1. calls sandbox_create(network="web") and gets a sandbox_id back;
2. calls sandbox_copy_in to copy install.sh from your transfer folder into the sandbox;
3. calls sandbox_run to execute it, then again to inspect new files, processes and services;
4. calls sandbox_copy_out to save a report into your transfer folder;
5. calls sandbox_destroy. Whatever the script did is gone.
## How it works
mermaid
flowchart LR
A["AI agent (Claude)"] -- "MCP (stdio)" --> S["vmware-sandbox-mcp"]
S -- "clone from, never start" --> B[("base VM clean snapshot")]
S -- "allowlisted vmrun calls" --> C[("sandbox linked clone")]
C -- "web mode only" --> P["filtering proxy"]
P --> I(("public internet"))
S --- T["transfer folder"]
S --- L["audit log"]
Every sandbox is a linked clone of one powered-off snapshot of a Linux VM that you prepare once. Before a clone boots for the first time, its settings are rewritten: no shared folders, no clipboard, no USB, no CD-ROM, and no network unless the agent asked for one.
## Requirements
A Windows host with VMware Workstation Pro and its vmrun command-line tool. Developed and tested on Workstation 25H2 (vmrun 1.17.0) on Windows 11. Linux hosts are not supported.
Python 3.11 or newer.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/rumenjordanov-vmware-sandbox-mcp/)
- Source
- awesome · https://github.com/rumenjordanov/vmware-sandbox-mcp
- Browse by field
- MCP servers
- Traction
- 2 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.