shanselman

sandbox-mcp: Test Windows Apps in Disposable Windows Sandbox

sandbox-mcp uses Windows Sandbox to test apps on fresh, disposable Windows 11 machines, with a CLI and optional MCP adapter for AI agents. It captures UI, process, crash, and installer evidence, helping developers check how apps behave on a clean customer PC.

NewJavaScriptMITWindowsMCP ServerTesting
Stars
452
Forks
22
Last commit
1 day ago
Contributors
4
Releases, 12 months
3

Our take

Newless than six months old and changing fast

Health score

41/100

How it is scored
Activity
57
Community
23
Issues
21
Pull requests
62

This is a promising, actively changing Windows testing tool with substantial functionality, but its short history and reliance on one main contributor make it an early-stage choice.

Good fit if

  • You need repeatable clean-machine checks for Windows desktop apps and can run Windows Sandbox on a supported Windows edition.
  • Your workflow benefits from UI Automation, installer audits, or durable test evidence rather than only checking whether an app launches.
  • You want an optional MCP interface for an agent, or prefer to use the standalone CLI.

Look elsewhere if

  • You need Linux, Windows Home or Windows Server support, parallel sandbox guests, or persistent guest machines.
  • Your work requires a broad, mature contributor base: most recent project activity comes from one person, despite contributions from others.
  • You need a general malware-analysis lab or assurance that every Windows app and hardware-dependent workload will work in Sandbox.
All health signals
Last commit2026-11-15 (1 day ago)
Commits, last 90 days61
Releases, last 12 months3 (latest v1.2.0, 2026-11-07)
Contributors4 (top contributor: 90% of commits)
Issues closed, last 90 days0
Pull requests merged, last 90 days5 (typically merged in 0 days)
Project age10 days

Checked on 2026-11-17 with the GitHub API.

Project history

Daily GitHub snapshots since Nov 17, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

456

Forks

24

More snapshots will appear as the daily collection continues.

Overview

sandbox-mcp is a Windows Sandbox automation tool for checking how Windows apps behave on a fresh, disposable Windows 11 machine. Its sbx CLI and optional MCP server share the same engine, which boots a guest, deploys or installs an app, runs checks, collects evidence, and destroys the guest. This targets the gap between an app working on a developer’s machine and working on a clean customer PC.

The project is for Windows developers and AI agents that need to test real desktop apps without using the developer’s own desktop. It supports UI Automation, screenshots, crash checks, installer and uninstaller audits, and observations of untrusted files. Windows Sandbox is available on Windows 11 Pro, Enterprise, or Education, not Windows Home or Windows Server.

Key Features

  • Run an app in a fresh Windows Sandbox guest and keep reports and evidence on the host after teardown.
  • Use native UI Automation to inspect controls and interact with WinForms, WPF, Win32, and WinUI apps.
  • Test MSIX and other packaged apps, as well as executable and folder-based apps.
  • Diagnose likely app dependencies on the host, with runtime provisioning available only when explicitly requested.
  • Test installers and uninstallers by comparing system snapshots and reporting leftovers such as files, registry keys, services, and autoruns.
  • Detonate supported files in an isolated guest and report observed processes, network activity, persistence, and changes.
  • Capture screenshots and bounded recordings, with optional MCP tools that can return screenshots inline.

Use Cases

  • A Windows app developer can check whether a fresh customer machine has the runtime needed to launch an app, and retain the failure report and screenshot.
  • A QA engineer can automate a desktop smoke test through UI Automation without relying on pixel coordinates for ordinary controls.
  • An installer developer can see what an uninstall leaves behind and use the results to improve cleanup.
  • An AI-agent developer can let an agent build, test, and inspect a Windows app in a disposable guest rather than the user’s desktop.
  • A security-conscious user can observe the behavior of a suspicious script or installer in an isolated guest, with networking disabled by default for detonation.

What you need

Detected in the repository

  • Node.js >=20 (from package.json)
  • A test suite and automated checks on GitHub Actions

License in plain words

MITpermissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the copyright and license notice
  • Share your changes: no

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Download a Windows x64 portable ZIP from the GitHub releases page, extract it, and run the readiness check in PowerShell:

.\sbx.cmd doctor

The portable package includes a runtime, so a separate Node.js installation is not required. See the README for enabling Windows Sandbox, running a first test, and configuring an MCP client.

Considerations

  • The project is new and changing quickly. It has recent development activity and releases, but most of the code comes from one person, so teams should assess maintenance continuity before depending on it.
  • Running from source requires Node.js 20 or later. The portable Windows x64 release bundles a runtime; ARM64 is not currently packaged.
  • The host needs Windows 11 24H2 or later, a supported Windows edition, virtualization, and a logged-in desktop session. Windows Sandbox permits only one guest at a time.
  • Fresh guests do not retain installed apps or prerequisites. Dependency diagnosis is a conservative scan, and provisioning changes the result from a clean-machine test to a provisioned test.
  • The project notes that Windows Sandbox is not a guarantee against a hypervisor escape and is not a dedicated malware-analysis lab.
  • The repository is MIT licensed.

Found this useful?

Share it with someone who would like sandbox-mcp.