Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_QEMU_LAB_WORKSPACEYesThe absolute path to the directory where mcp-qemu-lab will store its workspace, logs, and artifacts.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
ensure_dependenciesB

Checks and auto-installs host dependencies, prepares workspace, and records versions.

vm_createC

Create a VM definition, disks, and cloud-init seed image.

vm_startC

Start a VM and return QMP/SSH endpoints.

vm_statusB

Get VM runtime/QMP/SSH status and log file paths.

vm_stopC

Stop a VM gracefully or forcefully.

vm_snapshot_saveC

Save a VM snapshot by name via QMP HMP bridge.

vm_snapshot_loadC

Load a VM snapshot by name via QMP HMP bridge.

guest_execC

Execute an allowlisted guest command over SSH, with optional per-call unsafe override.

guest_copy_outC

Copy a file artifact out of the guest and return artifact metadata.

guest_copy_inC

Copy a host file into the guest filesystem via SCP.

process_listC

List guest processes with pid, user, and cmdline.

process_mapsB

Return parsed /proc//maps for a guest process.

process_dump_coreC

Generate a process core dump in guest via gdb/gcore and copy artifact out.

guest_dump_memoryC

Dump full guest memory to a host artifact file via QMP.

debugger_attachC

Create an in-guest debugger session handle for a target PID.

debugger_set_breakpointC

Set breakpoint (symbol or address) for a debugger session.

debugger_continueC

Continue execution for debugger session.

debugger_read_registersC

Read process registers via in-guest gdb attach.

debugger_detachB

Detach and mark debugger session inactive.

artifacts_listB

List artifacts with hashes and provenance.

vm_logs_tailB

Fetch recent QEMU/serial/debug log tails and related audit lines for a VM.

guest_wait_readyB

Wait for guest SSH/cloud-init readiness and optional debugger dependencies (gdb).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Artifact IndexJSON index of all artifact metadata records.

TDQS

A3.5/5.0

Scored across 22 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no ambiguity, as they target specific actions on well-defined resources like VM operations, guest interactions, debugging, or process management. For example, vm_start, vm_stop, and vm_status are distinct lifecycle actions, while debugger_attach, debugger_continue, and debugger_detach are separate debugging steps.

Naming Consistency5/5

Tool names follow a highly consistent verb_noun pattern throughout, such as vm_start, guest_copy_in, debugger_attach, and process_list. This predictability makes it easy for agents to understand and select the right tool based on its naming convention.

Tool Count4/5

With 22 tools, the count is slightly high but reasonable for the comprehensive scope of QEMU lab management, covering VM lifecycle, guest operations, debugging, and process handling. It feels slightly heavy but each tool appears to earn its place without obvious redundancy.

Completeness5/5

The tool set provides complete coverage for the QEMU lab domain, including VM creation, start/stop/status, snapshot management, guest file operations, process debugging, and dependency checks. There are no apparent gaps that would hinder agent workflows, as all essential operations are supported.

Maintenance

ActivityInactive
ResponsivenessNo issues