blender-cu-vm-mcp
Enables AI agents to perform automated Blender UI testing and user-story validation through an isolated virtual machine, with tools for computer-use input, framebuffer screenshots, UI Automation trees, Blender bpy telemetry, scene state inspection, and snapshot rollback.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Blender Computer-Use Isolated Virtual Machine & MCP Server
An isolated, GPU-partitioned local Windows 11 Virtual Machine environment connected via Model Context Protocol (MCP) specifically engineered for AI coding agents to perform automated Blender UI testing, user-story validation, and Computer-Use workflows without disturbing your host desktop.
1. System Architecture
+---------------------------------------------------------------------------------------------+
| Coding Agents (Claude Code / OMP / Codex) |
+---------------------------------------------------------------------------------------------+
│
│ (MCP JSON-RPC via stdio)
▼
+─────────────────────────────────────────────────────────────────────────────────────────────+
| Host Layer: `blender-cu-vm-mcp` Server |
| - MCP Tool Handler (Computer Use, Analytical Inspection, Blender Telemetry, File Staging) |
| - VM Lifecycle Manager (Hyper-V Socket / PowerShell WMI / Sub-2s Snapshot Reset) |
+─────────────────────────────────────────────────────────────────────────────────────────────+
│
┌───────────────────────┴───────────────────────┐
│ Hyper-V Socket (HV-SOCK) / Internal VMSwitch │
▼ ▼
+───────────────────────────────────────────────+ +─────────────────────────────────────────+
| Windows 11 Guest VM (Hyper-V) | | Secondary (Fast CI): WSL2 Container |
| - NVIDIA GPU-PV (RTX 4080 Super vGPU: 8GB) | | - Mesa / Direct3D 12 GPU Accel |
| - Virtual Display Driver (1080p Fixed 60Hz) | | - Virtual X11 Display (Xvfb/Weston) |
| - Guest Agent Daemon (FastAPI / gRPC) | | - Guest Agent Daemon (Linux) |
| - In-Process Blender Telemetry Bridge (bpy) | | - Blender bpy IPC Bridge |
+───────────────────────────────────────────────+ +─────────────────────────────────────────+Related MCP server: WindowsPC-MCP
2. Key Features
Zero Host Disturbance: Synthetic mouse movements, drags, clicks, and keystrokes are executed exclusively inside the guest OS. Your real cursor and window focus remain completely untouched.
Hardware-Accelerated GPU Rendering: NVIDIA GPU-PV gives the guest VM near-native access to the host RTX 4080 Super (DirectX 12, Vulkan, OpenGL, and CUDA/OptiX).
Deterministic 1080p Display: Open-source Virtual Display Driver (
IddSampleDriver) locks the virtual screen to 1920x1080 @ 60Hz with 100% (96 DPI) scaling—preventing coordinate drift and sleeping monitors.Hybrid Multimodal Feedback: Agents receive:
Visual: Framebuffer screenshots with optional coordinate grid overlays.
Analytical: Windows UI Automation tree, bounding boxes, and window responsiveness.
Deep Telemetry: Blender
bpystate, active modifiers, node tree connections, and real-timestdout/stderrlogs.
Sub-2-Second State Rollback: Fast Hyper-V snapshot restoration resets the VM to a clean golden base after destructive or experimental runs.
3. Directory Layout
blender-cu-vm/
├── host/ # Host MCP Server & Hyper-V Controller
│ ├── mcp_server.py # Stdio JSON-RPC MCP server with 14 tools
│ ├── hv_transport.py # Hyper-V Socket (AF_HYPERV) & HTTP transport
│ ├── vm_controller.py # PowerShell WMI lifecycle & snapshot manager
│ └── asset_sync.py # Bi-directional file and addon staging
├── guest/ # Guest Agent Daemon (runs inside VM)
│ ├── guest_daemon.py # FastAPI HTTP/HV-SOCK unified server
│ ├── screen_capture.py # DXGI Desktop Duplication & visual diffs
│ ├── input_controller.py # Win32 SendInput (clicks, drags, typing)
│ ├── ui_automation.py # Windows UI Automation tree inspector
│ └── video_recorder.py # Hardware-accelerated NVENC MP4 recorder
├── blender/ # Blender Embedded Runtime Bridge
│ ├── cu_telemetry_bridge.py # Non-blocking TCP telemetry server
│ ├── crash_interceptor.py # C-level stdout/stderr stream tee
│ └── state_inspector.py # Declarative scene invariant checker
├── scripts/ # Automated Setup & Provisioning
│ ├── setup_vm_gpupv.ps1 # Automated Hyper-V Gen2 VM creator
│ ├── stage_gpupv_drivers.ps1 # NVIDIA GPU-PV driver packaging & injection
│ ├── setup_virtual_display.ps1 # Virtual display & autologon configuration
│ └── manage_golden_snapshot.ps1 # Instant snapshot creation & rollback
├── tests/ # Verification & E2E Test Suite
│ ├── test_blender_user_story.py # 12-stage automated test suite
│ └── verify_isolation.py # Zero host disturbance verification
├── mcp-config.json # Registration snippet for Claude Code / OMP
└── README.md4. Setup & Installation Guide
Step 1: One-Command Unattended Deployment (PowerShell as Administrator)
Provisions the VM if missing, builds the unattended bootstrap ISO
(scripts\build_bootstrap_media.ps1, IMAPI2 — no ADK needed), attaches it
alongside the Windows 11 install ISO, boots the VM, and polls the guest
daemon health endpoint until the fully-unattended chain
(OOBE → auto-logon → bootstrap.cmd → install_guest.ps1 → daemon on
192.168.122.100:8000) completes:
cd C:\tmp\blender-cu-vm
.\scripts\deploy_guest_os.ps1 -WindowsISO "C:\ISOs\Win11_24H2_English_x64.iso"
# Watch graphically at any time: vmconnect.exe localhost Blender-CU-VMStep 2: Stage NVIDIA GPU-PV Drivers (host side)
Mirror the host RTX 4080 Super driver binaries into the guest. Use Stage
before install, or OnlineCopy once the guest OS is running:
.\scripts\stage_gpupv_drivers.ps1 -VMName "Blender-CU-VM" -Mode "OnlineCopy"Step 3: Manual guest setup (only if not using the unattended path)
The unattended chain above already runs guest\install_guest.ps1 (static IP
192.168.122.100, GPU-PV drivers if staged, 1080p virtual display lock,
hidden daemon startup). To run it by hand inside the guest instead:
# From the bootstrap DVD drive (e.g. E:) or C:\BlenderCU\guest:
powershell -ExecutionPolicy Bypass -File .\install_guest.ps1Step 4: Create the Golden Base Snapshot
.\manage_golden_snapshot.ps1 -VMName "Blender-CU-VM" -SnapshotName "golden_base" -Action "Create"5. Connecting AI Coding Agents via MCP
Add the following to your ~/.claude.json or ~/.omp/agent/config.yml:
{
"mcpServers": {
"blender-cu-vm": {
"command": "python",
"args": [
"C:\\tmp\\blender-cu-vm\\host\\mcp_server.py"
],
"env": {
"BLENDER_VM_NAME": "Blender-CU-VM",
"BLENDER_GUEST_URL": "http://192.168.122.100:8000"
}
}
}
}6. Running Verification Tests
To verify all subsystems and run the simulated Blender user story:
python blender-cu-vm/tests/test_blender_user_story.py
python blender-cu-vm/tests/verify_isolation.pyTool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Windows computers for AI agents. Office, desktop apps, browser tasks, testing and file transfer.
Cloud desktops for AI agents: create a Linux computer, see its screen, click, type and run tasks.
Eyes and hands on real Windows PCs — observe, click, type via Glasswarp API.
Blender and GLB/FBX/USD/STL rendered on cloud GPUs for AI agents: product shots, turntables, MP4
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables autonomous desktop automation by delegating tasks to vision-based agents operating within cloud-based virtual machine sandboxes. It allows users to manage VMs, execute complex computer tasks, and receive text-based screen summaries across Linux, Windows, and macOS environments.2-
- AlicenseNot gradedqualityDmaintenanceGives AI agents their own virtual display on Windows, enabling isolated clicking, typing, and screenshots without interfering with the user's desktop.2MIT
- AlicenseBqualityBmaintenanceEnables coding agents to operate desktop apps or VMs, capture successful GUI runs as local workflow memories, and replay reusable tasks with visual checks.172MIT
- AlicenseBqualityCmaintenanceEnables AI coding agents to work inside a disposable Windows guest desktop, where they can run shell commands, launch applications, inspect and operate native GUI controls, perform browser DOM actions, and transfer files. Fresh observations, PNG screenshots, and hashed artifacts let agents verify results without touching the host desktop.18MIT