Lume ships a built-in Model Context Protocol (MCP) stdio server that exposes VM management operations as tools consumable by AI agents and MCP-compatible clients. Tool names useDocumentation Index
Fetch the complete documentation index at: https://mintlify.com/trycua/cua/llms.txt
Use this file to discover all available pages before exploring further.
snake_case.
Starting the MCP server
Start the server withlume serve --mcp:
MCP clients discover the live tool list automatically from the server. Always use client-side tool discovery to ensure the tool schemas match the installed Lume version. The tools documented here reflect Lume 0.5.3.
Available tools
The MCP server exposes tools for the full VM lifecycle. Thelume_resize_disk tool is documented in detail below. All other tools follow the same pattern — clients should discover their exact schemas at runtime.
lume_resize_disk
Grow a stopped VM’s disk to a new total size. The operation is increase-only — you cannot shrink a disk.
Name of the VM whose disk will be resized.
New total disk size as a human-readable string, e.g.
120GB. Must be greater than the current disk size.Named storage location or direct path to the VM. Uses the default location if omitted.
Skip the macOS rollback copy before resizing. Cannot be
true at the same time as keep_backup.Keep the rollback files on the host after a successful resize. Cannot be
true at the same time as no_backup.Validate and print the resize plan without modifying the disk. Useful for checking minimum size requirements before committing.
no_backupandkeep_backupare mutually exclusive.- The default rollback copy requires enough free host space for the RecoveryOS data and copy-on-write metadata.
- The first macOS resize must leave enough room to relocate RecoveryOS without overlapping its old location. Lume reports the minimum accepted total size.
- FileVault-encrypted macOS guests are not supported.
- The host must run the same or a newer macOS version than the guest.
VM lifecycle tools
The following tools are available but their schemas are version-specific. Use MCP client-side tool discovery to get the exact parameter schemas for your installed version.| Tool name | Purpose |
|---|---|
lume_list_vms | List all virtual machines managed by Lume. |
lume_get_vm | Get detailed information about a specific VM. |
lume_create_vm | Create a new virtual machine. |
lume_run_vm | Start a stopped virtual machine. |
lume_stop_vm | Stop a running virtual machine. |
lume_delete_vm | Delete a VM and its associated files. |
lume_clone_vm | Clone an existing VM to a new name. |
lume_exec | Execute a command in a VM via SSH. |
check_for_update | Check whether a newer Lume release is available. |
Telemetry and the MCP server
Lume records alume_mcp_session_started event when the stdio MCP server starts, and a lume_mcp_tool_completed event for each tool invocation. These events include only allowlisted, bounded properties — no tool arguments or results are recorded. See Telemetry and privacy for the full schema.