sandbox-mcp, released by Scott Hanselman, automates the built-in Windows Sandbox: agents can launch a clean Windows 11, deploy their own programs, use UI automation to read and interact with WinUI, WPF, WinForms, and Win32 interfaces, check for missing runtime libraries, and bring screenshots, screen recordings, exit codes, and crash events back to the host machine. The command-line tool sbx and the optional MCP service share the same engine; networking can be optionally disabled, firewalled, or open; it can also audit the behavior of installers and suspicious files.
Why it matters Reproduce "it works on my machine" issues in a fresh, network-isolated Windows sandbox, keeping screenshots, screen recordings, and crash information on the host, with the sandbox deleted after use.
Stars 480 (+29 / 24h)
Reasons
- 29 new stars in 24 hours, total stars 480 (indicating attention only); MIT license
- README includes a compatibility matrix and time costs for each configuration, along with known gaps
Usage
- Download the v1.2.0 portable package (with bundled Node.js) from Releases, or have the agent install it according to docs/agent-setup.md; then have it run your exe in a fresh sandbox and report missing dependencies
Risks
- Windows Sandbox is only available on Windows 11 Pro, Enterprise, and Education editions; it is not available on Home edition or Windows Server
- Enabling the sandbox feature for the first time requires administrator privileges and may require a restart