Windows Sandbox

Provides programmatic control over Windows Sandbox through MCP, enabling lifecycle, command execution, shared folders, network information, and session management.

other

1

GitHub Stars

other

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "yourtablecloth-windowssandboxmcp": {
      "command": "dnx",
      "args": [
        "WindowsSandboxMcp",
        "--yes"
      ]
    }
  }
}

You manage Windows Sandbox instances programmatically through MCP, giving you lifecycle control, in-sandbox command execution, file sharing, network information, and session monitoring. This MCP server enables you to automate and integrate Windows Sandbox capabilities with your MCP-enabled clients for streamlined testing and isolated workspaces.

How to use

Use an MCP client to communicate with the Windows Sandbox MCP server and perform actions like starting or stopping a sandbox, running commands inside the sandbox, sharing host folders, and retrieving status information. The server exposes a set of capabilities that let you orchestrate sandbox lifecycles, execute scripts, map folders, fetch network details, manage sessions, and monitor whether a sandbox is currently running.

How to install

Prerequisites you need before you start:

Windows 11 24H2 or later (sandbox architecture and wsB CLI needed)
.NET 10.0 SDK
Windows Sandbox feature enabled

Install and build the MCP server locally:

# Build the MCP server solution
dotnet build

Run the development version to verify the server is responsive. Use the explicit project path shown in the examples to start the server from your environment.

# Run the project in development mode (adjust the path to where you have the project)
dotnet run --project D:\projects\WindowsSandboxMcp\src\WindowsSandboxMcp\WindowsSandboxMcp.csproj

Configure your MCP client with an appropriate stdio server entry to point to the local runtime. You will provide the runtime command and arguments so the client can instantiate and talk to the MCP server.

Additional configuration and notes

Status and availability depend on the Windows Sandbox architecture introduced in Windows 11 24H2. Ensure your environment has wsB.exe access and the required Windows components. This MCP server is marked experimental and may have bugs or limitations. Provide feedback and report issues to help improve it.

Two example runtime configurations you can use in your MCP client setup to run the server locally are shown here. The first runs the server via the legacy CLI launcher, and the second runs it via the .NET runtime for development.

# Everyday-use stdio configuration (example with legacy launcher)
{
  "type": "stdio",
  "name": "windows_sandbox",
  "command": "dnx",
  "args": ["WindowsSandboxMcp", "--yes"]
}

# Development configuration using the project directly
{
  "type": "stdio",
  "name": "windows_sandbox_dev",
  "command": "dotnet",
  "args": ["run", "--project", "D:\\projects\\WindowsSandboxMcp\\src\\WindowsSandboxMcp\\WindowsSandboxMcp.csproj"]
}

Available tools

SandboxLifecycle

Manage the lifecycle of a Windows Sandbox instance, including start and stop operations with configurable options.

ExecCommand

Execute commands or scripts inside the running sandbox and receive output back in the MCP client.

SharedFolders

Map host directories into the sandbox to enable file sharing between the host and the sandbox environment.

NetworkInfo

Retrieve network configuration and IP addresses for the sandbox instance.

SessionManagement

Connect to and monitor active sandbox sessions to observe activity and status.

StatusMonitoring

Check the current running state of the sandbox and report readiness.