A
licenseNot graded
qualityD
maintenanceEnables AI agents to control and automate Incus/QEMU virtual machines via SSH, supporting mouse/keyboard, screenshots, commands, and lifecycle management.
MIT
qemu-mcp
by 0xmortuex
Related Servers
Alternatives to qemu-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceEnables MCP-capable agents to control a real QEMU virtual machine through nine computer-use tools—screenshot, click, move, type, key, scroll, status, start, and stop—without accessing the host’s pointer, clipboard, or files.9MIT
- FlicenseAqualityDmaintenanceEnables AI agents to capture high-quality screenshots from running QEMU virtual machines using the QEMU Machine Protocol (QMP), automatically discovering VMs and returning screenshots as PNG images.1-
- AlicenseNot gradedqualityBmaintenanceAn MCP server that controls self-hosted QEMU macOS VMs on Linux over QMP, letting agents capture screenshots and send clicks, drags, scrolls, typing, and key chords with no guest helper or Accessibility grant required.GPL 2.0
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with fully interactive terminal sessions, including TUI support, keyboard control, and screen capture across Windows, Linux, and Mac.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents direct control over QEMU virtual machines.17 npm1MIT
TDQS
A3.9/5.0
Scored across 21 tools
Disambiguation5/5
Each tool targets a clearly distinct action: boot/stop/pause/resume lifecycle, input (type/key/mouse), output (serial read/send, screenshot, waits), snapshots (save/load/delete/list), and disk/qmp utilities. The read-vs-write (qemu_serial vs qemu_serial_send) and serial-vs-screen wait pairs are explicitly distinguished in descriptions. qemu_qmp is a documented escape hatch that could overlap with pause/snapshot, but it's positioned as a raw fallback, not a primary path.
Naming Consistency4/5
All tools consistently use the qemu_ prefix in snake_case throughout, which is highly predictable. There is minor variation in verb placement—qemu_disk_create is object_verb while most others lead with a verb (qemu_boot, qemu_list), and the snapshot_* group uses a shared object prefix. Still very readable and internally coherent.
Tool Count4/5
21 tools is on the heavier side but each maps to a genuine VM-control concern (lifecycle, input, serial, snapshots, disk, version). The breadth is justified by the domain's surface area rather than being redundant. Slightly over the ideal but well-scoped.
Completeness5/5
Covers the full VM lifecycle: disk creation, boot, listing, pause/resume, graceful/forced stop, complete snapshot CRUD (save/load/delete/list), display and serial I/O, input injection, media swapping, version probe, and a raw QMP escape hatch. No obvious dead ends for agent-driven VM control.
Maintenance
ActivityActive
ResponsivenessNo recent community issues