Mcp Virtualbox

Created By
Eiliya Raizis3 months ago
Let AI see, click, type, and fully operate virtual machines
Overview

mcp-virtualbox

Let AI see, click, type, and fully operate virtual machines - from bare metal OS installation to daily use, no human needed.
30 tools that give AI full VirtualBox control through two modes:

  • Vision loop - screenshot the VM screen, read it, send keyboard/mouse input. Install any OS from any ISO without scripting.

  • Text mode - switch to SSH, WinRM, or Guest Additions for fast command execution once the OS is running.

Quick setup

Claude Code (easy install)

/plugin marketplace add chryaner/mcp-virtualbox /plugin install mcp-virtualbox@mcp-virtualbox

Manual

{
  "mcpServers": {
    "mcp-virtualbox": {
      "command": "npx",
      "args": ["-y", "mcp-virtualbox"]
    }
  }
}

Requires VirtualBox 7.x and Node.js 18+. Provide your own OS installer ISO.

What you can do

  • Install any OS from an ISO - the AI clicks through the entire installer
  • Test your app's installer on a clean Windows machine
  • Compile code on legacy Linux (CentOS 6, etc.)
  • Run legacy software that needs old Windows (XP, 2000)
  • Create disposable VMs for untrusted files
  • Set up dev environments on a different OS than your host

Server Config

{
  "mcpServers": {
    "mcp-virtualbox": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-virtualbox"
      ]
    }
  }
}
Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
Eiliya Raizis
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago