VAMP MCP
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.
See VAMP in 30 seconds
From the VAMP VS Code extension, open a VirtualBox guest and verify that its Debian desktop is live.

▶ Watch the English demo (0:30)
English and Korean video guides include the 30-second demo, installation and AI connection, architecture, and a hands-on VM lab.
Related MCP server: virtualization-mcp
Ask your AI to install VAMP
In Claude Code or Codex with terminal access to your Windows PC, paste this request:
https://github.com/wayfarer6/vamp-mcp
Install VAMP MCP on my Windows PC from the latest official release. Verify the package
checksum, connect it to this AI client, and list my VMs using the backend I use on
this PC (VirtualBox or Hyper-V) to confirm it works.https://github.com/wayfarer6/vamp-mcp
Install VAMP MCP on my Linux PC from the latest official release. Verify the package
checksum, connect it to this AI client, and list my VMs using the backend I use on
this PC (VirtualBox or KVM) to confirm it works.English first-run guide: web-chat prompts, install commands, screenshots, and the order CSV demo · English walkthrough video (3:02) · 한국어 가이드
Next video · VAMP MCP architecture in Korean (3:04). Follow a request from the AI client to the guest and compare VirtualBox, KVM, and Hyper-V.
English architecture video · VirtualBox, KVM and Hyper-V architecture (1:53).
How to use
Supported hosts: Windows and Linux. macOS is outside the supported host scope.
Hyper-V on Windows (experimental). Enable Hyper-V and select VM Manager → Connection → Virtualization platform → Hyper-V. VAMP can create and list VMs, launch VMConnect, and exchange files with supported Windows guests. Use VMConnect for the guest desktop. Hyper-V does not yet support the embedded viewer or saved desktop replay. Hyper-V setup and MCP tools
Windows MCP requirement. VAMP and VAMP Vault MCP servers require Windows administrator privileges. The vamp-mcp CLI can request UAC to start the server in a separate elevated process while the MCP client stays open. For a direct server command, start it from an administrator terminal. To use the MCP servers provided by the VS Code extensions, start VS Code with Run as administrator. Direct server startup exits when Windows has not granted administrator privileges.
Contributions are welcome. See the contribution guide and AI contributor instructions.
Run GUI automation inside a guest while you keep using your host desktop. With saved RPA, local replay can check the screen and output files without sending frames to a model. An external agent can receive screen data if its client requests it during exploration or targeted fallback. Vault-managed secrets can be delivered through the approved guest connection.
For SSH-based remote GUI automation, see the WSL2 remote MCP worker guide.
WSL2 remote MCP guides (English · 한국어).
Watch the VAMP overview in English for the architecture and first steps. The English installation guide starts on the Windows host with MCP package and VSIX installation and follows both routes through Debian startup in VirtualBox.
Watch the Windows VirtualBox Notepad verification in English or Korean. The Robot Framework run opens Notepad and checks the Windows (CRLF) status bar in a 1920×1080 guest.
Record in VirtualBox and add the Python script to the VS Code RPA Library
Generate a standalone Robot Framework package for a VirtualBox, SPICE, or VNC guest using the Windows Notepad sample recording.
Scratch repair verification in VirtualBox (English · Korean)
Codex ERP rehearsal, edited from actual guest captures and the reviewed source (English · Korean)
Codex ERP Robot Framework evidence includes the verification suite, reports, and sample CSVs.
Installed MCP replay after the ERP layout change (English labels · Korean labels).
Continuous Codex ERP showcase with captions, from authoring to the installed MCP rerun (English · Korean).
Run a reviewed VirtualBox scenario and get its CSV in MCP chat (current source build)
Export a decrypted copy of a file from a mounted VeraCrypt container with Vault MCP or VS Code (current source build)
💡 Why VAMP?
Computer-Using AI agents (CUA) are powerful, but they suffer from two fundamental problems in the real world:
Repeated screen analysis. A screenshot-driven agent may send new frames to a vision model as it makes decisions. Repeating the same workflow can incur the same model calls again.
The Environment Wall: Headless browsers and lightweight Docker containers fall flat when faced with native Windows desktop applications, enterprise ERPs, government portals, anti-bot software, and hardware security token checks.
VAMP introduces an elegant, token-efficient paradigm:
[1. Record Once] Human or CUA performs the task once on a clean VM.
│
[2. Package as RPA] VAMP converts the action into a deterministic Robot/Python script.
│
[3. Universal SSH] AI agents trigger the script over a unified SSH pipe with parameters.
│
[4. Zero-Token Check] Local YOLO & OCR daemons verify success inside the VM without streaming frames to the LLM.By decoupling execution logic from visual reasoning, VAMP avoids expensive multimodal roundtrips entirely for routine workflows, running deterministic RPA inside full hardware virtual machines (VT-x) and inspecting screens with local vision models only when verification or error handling is strictly needed.
⚖️ How VAMP Compares
Metric | Screen-driven CUA | Fixed recorded RPA | VAMP saved RPA |
Vision token cost | Provider usage depends on screenshot calls | No provider calls during fixed replay | Local replay and verification use no provider vision tokens. AI-assisted repair is measured separately. |
Execution latency | Includes screen-driven model calls | Includes scripted inputs and waits | Includes guest inputs, waits, and configured local checks |
After a layout change | Can inspect the new screen before acting | Requires explicit starting-screen and outcome checks to detect a mismatch | Can stop before input on a configured starting-screen mismatch and hand off for targeted repair |
Windows VirtualBox ERP check | Elapsed time | Verified outcome |
Saved replay on the original layout | 35.97 s | 17 actions and a fresh CSV with all three expected orders |
Saved replay after scratch verification and review | 54.44 s | 30 actions and a fresh CSV with the expected SHA-256 |
Robot Framework scenario across both layouts | 239.05 s | Two matching CSVs and zero inputs from the stale replay |
In a separate matched comparison with three runs per method and layout, VAMP saved replay verified all three v1 CSVs and stopped all three v2 runs before sending input. Fixed keyboard replay produced three incorrect v2 CSVs, and screen-driven CUA verified all six CSVs across both layouts. Median timings and evidence
⚡ Core Architecture & Highlights
1. 🌐 Universal SSH Control Plane
Forget OS-dependent orchestration. During Packer automated builds, VAMP automatically configures:
Windows 11: OpenSSH Server capability enabled, automatic service startup, port 22 firewall rule, and PowerShell configured as the default shell.
Debian:
openssh-serverpreseeded, auto-enabled, and passwordlesssudoset up for sandbox users.Result: AI agents interact with all guests through a single, standardized SSH pipe.
2. 🎛️ Virtualization Abstraction via Packer & Vagrant
VAMP abstracts the entire virtualization stack using HashiCorp Packer and Vagrant, enabling seamless support across diverse hypervisors and guest OSes:
Automated Image Provisioning (Packer): Builds clean, standardized golden images (
.box/ OVA / QCOW2) across Windows 11 and Debian with zero human intervention. Automatically injects guest drivers (VirtIO / Guest Additions) and provisions OpenSSH.Unified Runtime Lifecycle (Vagrant & DesktopAdapter): Wraps VM creation, boot, snapshots, and networking behind a common interface. Automatically resolves the optimal provider and plugins across VirtualBox, KVM (libvirt/QEMU), and Hyper-V.
Zero Hypervisor Boilerplate: AI agents and developers interact with the exact same MCP tools and SSH pipelines regardless of the host OS or underlying hypervisor engine.
3. 🚀 Instant Vision Preload (Zero Cold-Start)
VAMP MCP prepares its default OmniParser YOLO icon weights in the background at startup, checks their SHA-256, and reuses the user cache. Configured OCR and YOLO workers warm up without delaying the MCP handshake. Model setup and overrides
4. 🔐 Zero-Trust Credential Isolation (vamp-vault)
Encrypted KeePassXC (
.kdbx) and optional VeraCrypt (.vhd) volume storage.Credentials are piped exclusively via
stdindirectly into target tools—never passed via command-line arguments (argv), preventingps auxprocess table inspection.Strict Per-Host Boundary: Remote servers maintain their own independent vaults; credentials and master keys are never shared or synced between remote hosts.
5. 📦 Guest bootstrapping
VirtualBox fetches post-install resources over its build NAT. Hyper-V Windows uses the selected switch's host IPv4, while Hyper-V Debian reads offline answer media and uses a static network profile after installation. QEMU's default build NAT reaches the host at 10.0.2.2, independently of the deployed libvirt network. VM MCP setup and troubleshooting
For a Debian golden image on Hyper-V, prepare a dedicated internal switch with WinNAT and reserve a static guest address before starting the build. If an older image build stalled at Default Switch DHCP or network preseed, start a fresh build with the offline answer ISO. Keep the golden export separate from the live VM disk. Debian Hyper-V setup and recovery
🚀 Quick Start
1. Use MCP without VS Code
With Node.js 22+, download the standalone vamp-mcp and optionally vamp-mcp-vault tarballs from GitHub Releases. Verify the tarball hashes against RELEASE-SHA256SUMS, then install the packages you downloaded.
npm install -g ./vamp-mcp-0.3.13.tgz
vamp-mcp setup
# Optional Vault
npm install -g ./vamp-mcp-vault-0.1.15.tgzRegister VAMP MCP with command vamp-mcp and no arguments, and VAMP Vault with command vamp-mcp-vault and no arguments. If the client cannot resolve these commands, use their full installed paths. Do not add separate Podman or hypervisor registrations. See MCP registration.
2. Use the VS Code extensions
Download both VSIX files from GitHub Releases. Use Extensions: Install from VSIX separately for each file. Install VAMP MCP Tools first, wait for it to finish, then install VAMP Vault and reload VS Code.
Open the VAMP activity bar. Use Open VM Manager for VMs, Open Containers for the Podman inventory and desktop actions, and RPA Library for reviewed workflows. Manage credentials in VAMP Vault separately.
For WSL, follow the manual setup guide. See Container desktops for rootless Podman, noVNC, capture, and limitations.
For Windows host PowerShell policy and separate Hyper-V/CIM permission checks, see the Windows host guide.
After installing, check the VAMP entries with code --list-extensions --show-versions. The versions should match the two downloaded file names. If a bundled Marketplace version appears, reinstall the corresponding VSIX separately.
Record, replay, and repair a task
Set up the guest and use the same guest resolution for recording and replay. The Windows VirtualBox setup uses 1920×1080 after initialization.
In RPA Library, search for a reviewed workflow first. To create a new one, record the task in the guest, review the captured actions, and remove sensitive input before saving. For a standalone Robot Framework package, use the PyAutoGUI conversion guide.
Replay the reviewed workflow on the selected guest. Check the expected screen or output file before treating it as successful.
If the screen changed, inspect the affected area and propose a targeted repair. Test the repair in a separate VirtualBox guest, then review the verified revision before using it again. See the recording and repair workflow.
For Windows replay on VirtualBox or KVM with a local VNC display that may encounter a guest UAC prompt, enable pause_on_uac. The recording and guest display must both be 1920×1080. VAMP checks the guest screen with local OCR and stops for operator review. To continue the same run after approval in the guest console, also set uac_wait_seconds and a unique uac_resume_text that appears in the expected app. See the guest UAC replay workflow.
🏗️ Architecture Overview
flowchart TD
subgraph Host ["Host machine"]
Agent["AI agent / MCP client"]
MCP["VAMP MCP (vamp-mcp)"]
subgraph VaultService ["VAMP Vault MCP (vamp-mcp-vault)"]
Vault["Vault tools · user approval"]
DB["KeePassXC KDBX · credentials and volume owner agent IDs"]
VC["VeraCrypt"]
Vault --> DB
Vault --> VC
end
HTTP["Postinstall Script Server :8421"]
RPA["Robot Framework / Python RPA runner"]
Vision["Local YOLO / OCR workers"]
Desktop["Desktop adapter"]
Agent <-->|MCP Stdio Protocol| MCP
Agent <-->|MCP stdio · tools and receipts| Vault
MCP --> HTTP
MCP --> RPA
RPA -->|Keyboard and mouse| Desktop
Desktop -->|Captured frames| RPA
RPA -->|Selected images| Vision
Vision -->|Detections and text| RPA
end
subgraph Infrastructure ["Virtualization Abstraction Layer"]
Packer["Packer (Golden Image Provisioning)"]
Vagrant["Vagrant & DesktopAdapter"]
MCP --> Packer
MCP --> Vagrant
Packer -->|Golden Images| Vagrant
Vagrant -->|VirtualBox / KVM / Hyper-V| VM
end
VM["Isolated VM desktop"]
Container["Isolated desktop container"]
Disk["Assigned VeraCrypt volume"]
VC --> Disk
Disk -->|Secondary disk| VM
Disk -->|Scoped workspace| Container
Vault -->|Approved credential to configured receiver| VM
Vault -->|Approved credential to configured receiver| Container
Desktop <-->|Console capture and input| VM
Desktop <-->|Managed RFB capture and input| ContainerRobot Framework and Python run on the controller host, alongside the local YOLO and OCR workers. The desktop adapter captures the target's screen and sends keyboard and mouse events, as a person would through a VM console. With a remote VM, the remote hypervisor host handles console capture and input over SSH while the controller can analyze the returned frames locally. Supported operations depend on the desktop backend.
The MCP client calls VAMP MCP for desktop control and calls VAMP Vault MCP
separately for credentials and encrypted volumes. After user approval,
vault_deliver_credential sends a value directly to the configured receiver
and returns a delivery receipt over MCP.
🌐 Community Script Hub
Don't reinvent the wheel. Browse pre-built, community-verified RPA packages on the VAMP Script Hub:
Portal logins (Naver, Google, GitHub, Slack)
Enterprise PDF document generation
File extraction and scheduled status reporting
🔒 Responsible Use & Security
VAMP is built for research, productivity, and secure local automation.
User approval: Require explicit confirmation for sensitive actions.
Isolated Sandbox: Use sandboxed credentials and test environments. You remain responsible for all operations executed inside guest VMs.
Open Source: Licensed under the MIT License. Third-party components retain their respective licenses (see THIRD_PARTY_NOTICES.md).
Tool 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
Real desktops for AI agents, on machines you choose: screenshot, type, click, hire more agents.
Cloud desktops for AI agents: create a Linux computer, see its screen, click, type and run tasks.
Windows computers for AI agents. Office, desktop apps, browser tasks, testing and file transfer.
Persistent Linux computers for AI agents: desktop, signed-in browser, vault, apps and shell.
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-
- AlicenseBqualityBmaintenanceEnables AI assistants to manage virtual machines, sandboxes, and dev environments through VirtualBox, Hyper-V, and Windows Sandbox, supporting VM lifecycle, ISO downloads, networking, and unattended installs.920MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create, drive, checkpoint, reset and delete resettable Windows and Ubuntu desktop VMs on Apple Silicon Macs, giving them real desktops to click, type and screenshot in plus shell commands, file transfer and port forwarding. All processing is local, so agents can work in isolated guests without leaving the Mac.4MIT
- 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