virtualization-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vm_managementA | Virtual machine lifecycle management. Actions: list, create, start, stop, delete, clone, reset, pause, resume, info. For LLM config suggestions or sandbox workflow planning use vm_agentic_workflow. vm_name: required for all actions except list and clone. source_vm + new_vm_name: required for clone. os_type, memory_mb, disk_size_gb: required for create. Use system_management(action='ostypes') for valid os_type values. |
| network_managementB | Comprehensive network management portmanteau tool. This tool consolidates all network operations into a single interface. Use the 'action' parameter to specify which operation to perform. Different actions require different parameters. |
| snapshot_managementB | Comprehensive snapshot management portmanteau tool. This tool consolidates all VM snapshot operations into a single interface. Use the 'action' parameter to specify which operation to perform. All actions require vm_name, and most require snapshot_name. |
| storage_managementB | Comprehensive storage management portmanteau tool. This tool consolidates all storage operations into a single interface. Use the 'action' parameter to specify which operation to perform. Different actions require different parameters. |
| system_managementB | Comprehensive system management portmanteau tool. This tool consolidates system information and diagnostics operations into a single interface. Use the 'action' parameter to specify which operation to perform. Most actions don't require vm_name. |
| sandbox_managementA | Docker-based code sandbox management for safe, isolated code execution. Requires Docker Desktop running on the host. Two execution modes:
|
| vm_agentic_workflowB | Sampling-backed agentic operations for virtualization. Actions:
All actions use ctx.sample() when available; fall back to sensible defaults otherwise. |
| info_toolsA | Comprehensive tool discovery and help portmanteau tool. This tool consolidates application-specific help and introspection operations into a single interface. Provides information about available tools, their operations, and usage. Use the 'action' parameter to specify which operation to perform. Note: This is separate from MCP protocol's native tools/list method. MCP clients get tool schemas automatically - this tool provides app-specific help content and detailed introspection for users. |
| proxmox_managementC | [RATIONALE] Consolidated Proxmox VE management — single tool for all remote Proxmox operations. Only available when PROXMOX_HOST is configured in the environment. Operations:
Return Format{"success": bool, "message": str, "data": {...}} Examplesproxmox_management(operation="list_vms") proxmox_management(operation="start_vm", vmid="100") |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| virtualization_expert | Load instructions for acting as a virtualization expert using this MCP server's tools (VMs, snapshots, storage, networking). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| virtualization-expert/SKILL.md | Act as a virtualization expert using the Virtualization MCP tools (VMs, snapshots, storage, networking) |
| virtualization-expert/_manifest | File listing for virtualization-expert |
TDQS
Scored across 9 tools
Tools are grouped by distinct domains (network, storage, VM lifecycle, etc.), but the portmanteau pattern centralizes multiple operations into one tool via an 'action' parameter, which could cause minor confusion. However, descriptions are clear and domains are well-separated.
Most tools follow a '_management' suffix pattern, but 'info_tools' and 'vm_agentic_workflow' deviate. The naming is not strictly verb_noun but is readable and predictable once the pattern is understood.
9 tools cover the major aspects of virtualization (VMs, storage, network, snapshots, sandbox, system info, Proxmox, agentic workflows). The count is well-scoped and each tool earns its place.
The tool set covers VM lifecycle, storage, network, snapshots, sandbox execution, and system diagnostics. Minor gaps exist (e.g., no dedicated tool for advanced network configuration), but core workflows are well-supported.