QEMU

A Local MCP Server that enables QEMU-based Linux binary analysis via STDIO with VM control, memory dumps, in-guest debugging, and artifact resources.

python

0

GitHub Stars

python

Language

4 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
  "mcpServers": {
    "kevin4562-qemu-mcp": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/Kevin4562/QEMU-MCP.git",
        "mcp-qemu-lab"
      ]
    }
  }
}

You can run a Local MCP Server for Linux binary analysis inside QEMU guests using a STDIO-based MCP server. It enables VM lifecycle control, full guest RAM dumps, in-guest debugging workflows, per-process core dumps, and artifact indexing through MCP resources, all while keeping safety defaults in place.

How to use

To use this MCP server, install the MCP client tooling and start the server through the standard client workflow that fetches the server from its GitHub source. You will connect via STDIO, perform VM operations, and access in-guest tools and memory dumps through the MCP client. You can create, start, stop, and snapshot virtual machines, dump memory, attach debuggers, extract cores, and enumerate artifacts with associated metadata and content.

How to install

Prerequisites you need before running the MCP server:

Python 3.11+
uv
qemu-system-x86_64
qemu-img
ssh
scp
ssh-keygen

Run from GitHub URL

Fetch and run the MCP server directly from the repository using the MCP client runner. This approach does not require a local project path.

uvx --from git+https://github.com/Kevin4562/QEMU-MCP.git mcp-qemu-lab

Recommended pin (optional)

If you want to pin a specific branch, tag, or commit for stability, use the following form with the same runner.

uvx --from git+https://github.com/Kevin4562/QEMU-MCP.git@main mcp-qemu-lab

Available tools

vm_create

Create a new virtual machine instance with configurable resources and boot options.

vm_start

Start a created virtual machine and initialize its lifecycle within the MCP framework.

vm_status

Query the current status of a running or stopped VM.

vm_stop

Stop a running virtual machine and preserve or discard its state according to the workflow.

vm_snapshot_save

Capture a VM state snapshot for later restoration.

vm_snapshot_load

Restore a VM from a previously saved snapshot.

guest_wait_ready

Wait for the guest to become ready for further actions, with optional safety checks.

guest_exec

Execute a command inside the guest and capture output and exit status.

guest_copy_in

Copy files from the host into the guest filesystem.

guest_copy_out

Copy files from the guest filesystem back to the host.

process_list

List processes running inside the guest.

process_maps

Retrieve memory mappings for processes inside the guest.

debugger_attach

Attach an in-guest debugger to a target process.

debugger_set_breakpoint

Set a breakpoint in the target process for debugging.

debugger_continue

Continue execution after hitting a breakpoint.

debugger_read_registers

Read CPU registers from the in-guest debugger session.

debugger_detach

Detach the in-guest debugger from the target process.

process_dump_core

Dump a core file for a selected process from the guest.

guest_dump_memory

Dump a range of memory from the guest for analysis.

artifacts_list

List artifacts and their metadata stored by the MCP server.

vm_logs_tail

Tail logs from the running VM for live debugging and observability.

artifact://{artifact_id}

Access artifact content stored by the MCP server.

artifact-index://all

Query the metadata index for all stored artifacts.