What can you do with this server?

anyvm-mcp is an MCP server that lets AI assistants boot and manage virtual machines (BSD, Linux, illumos, Haiku, Android, GNU Hurd, Plan 9) using natural language commands via QEMU. * List supported OSes: Discover all bootable guest OSes — FreeBSD, OpenBSD, NetBSD, DragonFly BSD, GhostBSD, MidnightBSD, Solaris, OmniOS, OpenIndiana, Tribblix, Haiku, Ubuntu, openEuler, BlissOS (Android), Debian GNU/Hurd, and Plan 9 — along with SSH users and notes. * Boot VMs: Launch VMs in the background with configurable OS, release version, CPU count, memory, architecture (x86_64, aarch64, riscv64, sparc64, powerpc64, s390x, etc.), port mappings, volume mounts, folder sync method (rsync/sshfs/nfs/scp/9p), snapshot mode, and boot timeout. * List running VMs: View all booted VMs with live running/stopped status, SSH ports, and log locations. * Get VM details: Retrieve state, SSH port/user/key, and serial log path for a specific VM. * Execute commands: Run shell commands over SSH inside a running VM (not available for Plan 9, which has no SSH). * Stop VMs: Gracefully shut down via SSH with ACPI fallback, or force-kill via QEMU monitor. * Read console output: Tail the serial console log to debug boot failures — works even without SSH, and is the only way to view Plan 9 output. * AI assistant integration: Works with MCP-compatible assistants like Claude Code and GitHub Copilot for natural language VM control.

Which integrations are available for this server?

Allows booting and managing Android (BlissOS) VMs with natural language, including SSH execution and serial console access. Allows booting and managing various BSD VMs (FreeBSD, OpenBSD, NetBSD, DragonFly BSD, GhostBSD, MidnightBSD) with natural language, including SSH execution and serial console access. Allows booting and managing Debian GNU/Hurd VMs with natural language, including SSH execution and serial console access. Allows booting and managing FreeBSD VMs with natural language, including SSH execution and serial console access. Allows booting and managing GNU Hurd VMs with natural language, including SSH execution and serial console access. Allows booting and managing Linux VMs (Ubuntu, openEuler) with natural language, including SSH execution and serial console access. Allows booting and managing NetBSD VMs with natural language, including SSH execution and serial console access. Allows booting and managing OpenBSD VMs with natural language, including SSH execution and serial console access. Allows booting and managing Ubuntu VMs with natural language, including SSH execution and serial console access.

How do I use anyvm-mcp?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@anyvm-mcp create a FreeBSD 14 VM named 'dev' with 2 CPUs and 2GB RAM" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

anyvm-mcp

Official

by anyvm-org

Overview Schema Source Related Servers Discussions Admin

Python

Local

anyvm-mcp

MCP server for anyvm -- boot and manage BSD, illumos, Linux, Haiku, Android, GNU Hurd, and Plan 9 VMs with natural language. Works with Claude Code, GitHub Copilot, and any other MCP-compatible AI assistant.

Overview

anyvm-mcp is a Model Context Protocol (MCP) server that bridges AI coding assistants with the anyvm VM launcher. anyvm boots prebuilt guest images under QEMU -- no manual installation, no libvirt. Once installed, your AI assistant can:

Boot FreeBSD, OpenBSD, NetBSD, DragonFly BSD, GhostBSD, MidnightBSD, Solaris, OmniOS, OpenIndiana, Tribblix, Haiku, Ubuntu, openEuler, BlissOS (Android), Debian GNU/Hurd, and Plan 9 guests in the background
Target x86_64, aarch64, riscv64, sparc64, powerpc64, s390x and more (per-OS availability varies)
Execute commands inside running VMs over SSH for instant diagnostics
Read the serial console to debug boot failures
Map ports and sync folders (rsync / sshfs / nfs / scp / 9p) between host and guest
Stop VMs gracefully (guest shutdown with an ACPI fallback) or hard-kill via the QEMU monitor

The VM model mirrors the anyvm CLI: a VM is identified by its OS name plus optional release (e.g. freebsd + 14.3), not by user-invented names. The first boot of an OS/release downloads the image from the matching anyvm-org builder release, so allow several minutes; later boots reuse the cached image.

Related MCP server: ProxmoxEmCP

Requirements

Requirement	Notes
Python >= 3.10
QEMU	`qemu-system-*` on PATH (anyvm can also self-download pinned builds for some guests)
OpenSSH client	`ssh` on PATH (used for exec/stop)
An MCP-compatible AI assistant	Claude Code, GitHub Copilot in VS Code, or any other MCP client

Note: The anyvm.py launcher is bundled automatically -- no separate installation needed.

Installation

pipx install anyvm-mcp

Or with pip:

pip install anyvm-mcp

Or install from source:

git clone https://github.com/anyvm-org/mcp
cd mcp
pip install -e .

Quickstart

Claude Code

Add the server to ~/.claude/mcp.json (or the project-level .claude/mcp.json):

{
  "mcpServers": {
    "anyvm": {
      "command": "anyvm-mcp"
    }
  }
}

Restart Claude Code. You can now say things like:

"Boot a FreeBSD 14.3 VM with 2 CPUs and 2 GB RAM, then run uname -a in it."

"My OpenBSD VM won't answer SSH. Show me the serial console output and suggest a fix."

GitHub Copilot (VS Code)

Add the server to .vscode/mcp.json in your workspace (or the user-level settings):

{
  "servers": {
    "anyvm": {
      "type": "stdio",
      "command": "anyvm-mcp"
    }
  }
}

Generic MCP client (HTTP/SSE)

Run anyvm-mcp as an HTTP server:

anyvm-mcp --transport sse --host 127.0.0.1 --port 8000

Then point your MCP client at http://127.0.0.1:8000/sse.

CLI reference

usage: anyvm-mcp [-h] [--anyvm PATH] [--data-dir DIR]
                 [--transport {stdio,sse,streamable-http}]
                 [--host HOST] [--port PORT]

options:
  --anyvm PATH          Path to the anyvm launcher (default: bundled anyvm.py)
  --data-dir DIR        Directory for images, logs, and VM state (default: ~/.anyvm-mcp)
  --transport           MCP transport: stdio (default), sse, or streamable-http
  --host HOST           Bind host for HTTP transports (default: 127.0.0.1)
  --port PORT           Bind port for HTTP transports (default: 8000)

Available tools

Tool	Description
`list_supported_os`	Every guest OS anyvm can boot, with notes and SSH user
`start_vm`	Boot a guest in the background (os, release, arch, mem, cpus, ports, volumes, sync)
`list_running_vms`	Registered VMs with a live running/stopped probe
`vm_info`	State, SSH port/user/key, and serial-log path for one VM
`exec_in_vm`	Run a shell command over SSH inside a running VM
`stop_vm`	Graceful guest shutdown (SSH + ACPI fallback); `force` hard-kills via QEMU monitor
`console_output`	Tail the VM serial console log (works even when SSH is down)

Notes:

start_vm separates OS and release: os="freebsd", release="14.3" -- omit release for the builder's default release.
Plan 9 (9front) guests have no SSH; exec_in_vm is unavailable for them. Use console_output, or the VNC web console anyvm prints at boot.
Haiku's SSH user is user; all other guests use root.

Example conversations

Boot and inspect a VM

You:      Boot an OmniOS VM with 4 CPUs and 4 GB RAM and show me its uname.
Copilot:  [calls start_vm(os="omnios", cpus=4, mem_mb=4096)]
          VM omnios-r151054 is running (ssh -p 42761 root@127.0.0.1).
          [calls exec_in_vm(os="omnios", command="uname -a")]
          SunOS omnios 5.11 omnios-r151054 i86pc i386 i86pc

Debug a boot failure

You:      My NetBSD VM never comes up on SSH. What's wrong?
Copilot:  [calls console_output(os="netbsd", lines=200)]
          The console shows the kernel waiting on root device selection...

Cross-architecture testing

You:      Run my test script on Ubuntu riscv64.
Copilot:  [calls start_vm(os="ubuntu", arch="riscv64",
                          volumes=["/home/me/proj:/proj"], sync="rsync")]
          [calls exec_in_vm(os="ubuntu", command="cd /proj && sh run-tests.sh")]

Development

# Install with dev dependencies
pip install -e ".[dev]"

# Run tests
pytest

# Run a single test file
pytest tests/test_vm_manager.py -v

License

MIT -- see LICENSE.

Available Tools

7 tools

console_outputA

Tail the VM's serial console log. Works even when SSH is down -- the tool for debugging boot failures, and the only way to see plan9 output.

Inputs: os (required), lines, release. Returns: result

exec_in_vmA

Execute a shell command over SSH inside a running VM and return the combined stdout/stderr. Not available for plan9 (no SSH).

Inputs: os (required), command (required), release, timeout_sec. Returns: result

list_running_vmsA

List all VMs this server has booted, with a live running/stopped state probe, SSH ports, and log locations.

Inputs: no named parameters. Returns: result

list_supported_osA

List every guest OS anyvm can boot (BSDs, illumos, Linux, Haiku, Android/BlissOS, GNU Hurd, Plan 9), with notes and the SSH user.

Inputs: no named parameters. Returns: result

start_vmA

Boot a guest VM in the background. The first boot of an OS/release downloads the image (hundreds of MB -- allow several minutes). Returns SSH connection details on success. OS and release are separate: os='freebsd' release='14.3', not 'freebsd-14.3'. Omit release to get the default release.

Inputs: os (required), arch, cpus, sync, +6 more.

stop_vmA

Stop a running VM: graceful guest shutdown over SSH with an ACPI fallback; force=true hard-kills QEMU via its monitor.

Inputs: os (required), force, release. Returns: result

vm_infoB

Detailed info about one VM (state, SSH port/user/key, serial log path). Identify the VM by OS name and optional release.

Inputs: os (required), release.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

Deploy Server

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored 2026-07-27 02:13 across 7 tools

Disambiguation5/5

Each tool has a distinct purpose: listing supported OS, executing commands, viewing console, starting, listing all VMs, getting VM info, and stopping VMs. No overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (list_supported_os, exec_in_vm, start_vm, etc.) with no deviations.

Tool Count5/5

7 tools cover the core VM lifecycle (start, stop, exec, console, list, info) and supported OS queries, which is well-scoped for the server's purpose.

Completeness4/5

Covers most essential operations: start, stop, execute commands, console output, listing, and details. Missing destroy/reboot but still functional.

Maintenance

ActivityInactive

ResponsivenessNo recent community issues

Resources

Related MCP Connectors

BoxCompute
ai.boxcompute
Linux VMs for AI agents: create VMs, run commands, edit files and open preview URLs.
Virtualization Code Execution Command Line
1
https://mcp.boxcompute.ai/mcp
Mandala Computer
io.github.mandalacomputer
Cloud desktops for AI agents: create a Linux computer, see its screen, click, type and run tasks.
Agent Orchestration Virtualization OS Automation
1
https://app.mandala.computer/mcp
emisar
dev.emisar
Let AI operate servers without SSH. Choose actions, approve risky changes, and audit every step.
Cloud Platforms Security Networking & Infrastructure
2375
https://emisar.dev/api/mcp/rpc
Runtime CloudA
com.withruntime
Linux microVM sandboxes for AI agents: run commands, files, processes, pause and wake.
Code Execution Virtualization Command Line
11
https://api.withruntime.com/mcp

Related MCP Servers

virtualization-mcp
Virtualization Developer Tools
sandraschi
A
license
B
quality
B
maintenance
Enables 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.
Updated 6 days ago (2026-11-06 03:09 UTC)
9
19
MIT
ProxmoxEmCP
Virtualization Observability
PureGrain
A
license
Not graded
quality
D
maintenance
Enables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, and cluster operations via natural language.
Updated 6 months ago (2026-04-27 15:45 UTC)
MIT
QVMConsole MCP Server
Virtualization OS Automation
QVMConsole
A
license
Not graded
quality
D
maintenance
Enables AI assistants to manage virtual machines via natural language, including creating, editing, and VNC control.
Updated 4 months ago (2026-07-12 10:52 UTC)
9 npm
MIT
Proxmox VE MCP Server
Virtualization Autonomous Agents
MTDEV2312
F
license
B
quality
D
maintenance
Enables natural language management of Proxmox VE VMs and containers, including lifecycle, snapshots, cloud-init, and secure multi-step automation workflows.
Updated 3 months ago (2026-08-01 02:09 UTC)
65
-

anyvm-mcp

Overview

Requirements

Installation

Quickstart

Claude Code

GitHub Copilot (VS Code)

Generic MCP client (HTTP/SSE)

CLI reference

Available tools

Example conversations

Boot and inspect a VM

Debug a boot failure

Cross-architecture testing

Development

License

Available Tools

Tool Schema Changelog

TDQS

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

virtualization-mcp

ProxmoxEmCP

QVMConsole MCP Server

Proxmox VE MCP Server