Proxmox VE MCP Server
Provides comprehensive management and automation for Proxmox VE clusters, including VM and container lifecycle management, snapshot and rollback, hardware tuning, migration, and cloud-init integration.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Proxmox VE MCP Server List all VMs and show their CPU and memory usage"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Proxmox VE MCP Server
A production-ready Model Context Protocol (MCP) server built with FastMCP for high-level Proxmox VE homelab and cluster automation. Rather than acting as a plain REST API wrapper, proxmox-mcp provides semantic, domain-driven orchestration capabilities for LLM agents (Claude Desktop, Cursor, Gemini CLI, etc.).
Table of Contents
Related MCP server: Proxmox MCP Server
Features
Full VM (QEMU) & LXC Container Lifecycle Management: Create, clone, start, stop, shutdown, reboot, pause, resume, migrate, and purge virtual machines and containers.
Hardware & Resource Tuning: Dynamically update CPU cores, sockets, RAM, disk sizes, network interfaces, and storage volume bindings.
Cloud-Init Integration: Inject user accounts, passwords, SSH keys, network configurations, and trigger ISO regeneration directly.
Snapshot & Rollback Tree: List, create, rollback, and delete snapshots for both VMs and LXC containers.
Multi-Step Workflows: Automated step-by-step provisioning, bulk operations across host targets, pre-backup snapshots with
vzdumpexecution, and cluster readiness checks with automatic rollback safety.Enterprise-Grade Security: CIDR-based client IP whitelisting, RBAC permission scopes (
READ_ONLY,OPERATOR,ADMIN), mandatory destructive operation confirmations (confirm=true), recursive sensitive payload scrubbing, and structured audit logs.
Prerequisites & Installation
Prerequisites
Python 3.12+ installed on the local system.
uv (recommended high-performance package manager) or standard
pip.Access to a Proxmox VE (v7.x or v8.x) server over HTTPS (port 8006).
Installation via uv (Recommended)
# Clone repository
git clone https://github.com/your-org/proxmox-mcp.git
cd proxmox-mcp
# Create virtualenv and install dependencies
uv venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
uv sync --all-extrasInstallation via pip
python -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
pip install -e ".[dev]"Environment Configuration
Configure connection and security settings via environment variables or a .env file in the root directory:
# Proxmox VE Connection Parameters
PROXMOX_HOST=Your_IP:8006
PROXMOX_USER=User@permision
PROXMOX_PASSWORD=Password
# Or API Token authentication (recommended):
PROXMOX_TOKEN_ID=Your_Token_ID
PROXMOX_TOKEN_SECRET=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
PROXMOX_VERIFY_SSL=false
PROXMOX_TIMEOUT=30.0
PROXMOX_MAX_RETRIES=3
# MCP Security & Authorization Settings
MCP_PERMISSION_LEVEL=operator
MCP_AUDIT_ENABLED=true
MCP_AUDIT_LOG_PATH=audit.log
MCP_ALLOWED_CLIENT_IPS=127.0.0.1/32,192.168.1.0/24Configuration Parameters Reference
Variable | Type | Default | Description |
| String | Required | Host address and port of Proxmox VE instance |
| String |
| Proxmox VE user identity |
| String |
| User password for API ticket authentication |
| String |
| API Token ID (takes precedence if provided) |
| String |
| API Token Secret key |
| Boolean |
| Verify TLS certificates |
| Float |
| HTTP request timeout in seconds |
| Integer |
| Maximum retry attempts on transient network errors |
| Enum |
| Baseline permission scope ( |
| Boolean |
| Enable JSON lines structured audit logging |
| Path |
| Path to append structured audit records |
| String |
| Comma-separated CIDR subnets allowed to execute MCP commands |
MCP Client Setup
Claude Desktop
Add the server configuration to your claude_desktop_config.json:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"proxmox-mcp": {
"command": "uv",
"args": [
"--directory",
"/path/to/proxmox-mcp",
"run",
"proxmox-mcp"
],
"env": {
"PROXMOX_HOST": "Your_IP:8006",
"PROXMOX_USER": "user@permission",
"PROXMOX_PASSWORD": "Password",
"PROXMOX_VERIFY_SSL": "false",
"MCP_PERMISSION_LEVEL": "operator"
}
}
}
}Cursor
Add to your project .cursor/mcp.json or Global MCP Settings:
{
"mcpServers": {
"proxmox": {
"command": "uv",
"args": [
"--directory",
"C:/Users/username/DEV/proxmox-mcp",
"run",
"proxmox-mcp"
],
"env": {
"PROXMOX_HOST": "Your_IP:8006",
"PROXMOX_TOKEN_ID": "user@permission!mcp_token",
"PROXMOX_TOKEN_SECRET": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"PROXMOX_VERIFY_SSL": "false"
}
}
}
}Gemini CLI
Configure gemini MCP extension in settings or execution config:
{
"mcpServers": {
"proxmox-automation": {
"command": "python",
"args": [
"-m",
"proxmox_mcp.main"
],
"cwd": "/opt/proxmox-mcp",
"env": {
"PROXMOX_HOST": "Your_IP:8006:8006",
"PROXMOX_USER": "user@permission",
"PROXMOX_PASSWORD": "Password"
}
}
}
}SSE Transport Mode
For standalone remote daemon deployment via Server-Sent Events (SSE):
# Start FastMCP server in SSE mode on port 8000
fastmcp run src/proxmox_mcp/main.py --transport sse --port 8000FastMCP Catalog
Tools
1. QEMU Virtual Machine Domain (vm)
Tool Name | Scope | Confirm? | Description |
| READ_ONLY | No | List VMs across cluster or specific node |
| READ_ONLY | No | Retrieve detailed status for a specific VM |
| READ_ONLY | No | Inspect hardware and operational config |
| OPERATOR | No | Create new QEMU virtual machine |
| OPERATOR | No | Clone existing VM or template |
| ADMIN | Yes | Purge VM and associated storage volumes |
| OPERATOR | No | Power on virtual machine instance |
| OPERATOR | Yes | Force stop virtual machine process |
| OPERATOR | Yes | Graceful OS shutdown with timeout |
| OPERATOR | Yes | Graceful OS reboot sequence |
| OPERATOR | No | Pause execution (suspend-to-RAM) |
| OPERATOR | No | Resume execution of paused VM |
| OPERATOR | No | Suspend VM state to storage disk |
| OPERATOR | No | Convert VM into immutable template |
| OPERATOR | No | Reconfigure CPU cores, sockets, NUMA settings |
| OPERATOR | No | Hotplug or adjust allocated RAM memory |
| OPERATOR | No | Expand virtual disk volume size |
| OPERATOR | No | Attach additional storage disk volume |
| ADMIN | Yes | Detach and remove storage disk volume |
| OPERATOR | No | Relocate disk volume to target storage pool |
| OPERATOR | No | Reconfigure virtual network interface card |
| OPERATOR | No | Set Cloud-Init user, password, SSH key, IP |
| OPERATOR | No | Trigger Cloud-Init ISO image regeneration |
| READ_ONLY | No | List snapshot tree for target VM |
| OPERATOR | No | Create named point-in-time VM snapshot |
| ADMIN | Yes | Restore VM state to target snapshot |
| ADMIN | Yes | Remove target snapshot from tree |
| ADMIN | Yes | Live or offline VM migration to target node |
2. LXC Container Domain (lxc)
Tool Name | Scope | Confirm? | Description |
| READ_ONLY | No | List LXC containers on cluster or node |
| READ_ONLY | No | Get detailed container runtime state |
| READ_ONLY | No | Inspect LXC container configuration |
| OPERATOR | No | Provision new LXC container |
| OPERATOR | No | Clone existing container instance |
| ADMIN | Yes | Destroy LXC container permanently |
| OPERATOR | No | Start LXC container execution |
| OPERATOR | Yes | Hard stop LXC container |
| OPERATOR | Yes | Graceful container shutdown |
| OPERATOR | Yes | Reboot LXC container |
| OPERATOR | No | Convert LXC container into template |
| OPERATOR | No | Update container hostname |
| OPERATOR | No | Update search domain and DNS nameservers |
| OPERATOR | No | Set root user password |
| OPERATOR | No | Append public SSH keys for root access |
| OPERATOR | No | Expand container root filesystem disk |
| OPERATOR | No | Adjust RAM and swap limits |
| OPERATOR | No | Adjust CPU cores and execution limits |
| READ_ONLY | No | List attached storage mount points |
| OPERATOR | No | Attach host bind mount to container |
| ADMIN | Yes | Detach host bind mount point |
| OPERATOR | No | Enable nesting feature for Docker support |
| OPERATOR | No | Enable keyctl subsystem inside container |
| OPERATOR | No | Mount FUSE filesystems inside container |
| READ_ONLY | No | List snapshot tree for LXC container |
| OPERATOR | No | Create named LXC container snapshot |
| ADMIN | Yes | Revert container state to snapshot |
| ADMIN | Yes | Remove snapshot from container tree |
3. Support Domains (cluster, nodes, storage, tasks)
Tool Name | Domain | Scope | Description |
| cluster | READ_ONLY | Evaluate quorum, node state, and storage health |
| cluster | READ_ONLY | Summarize cluster-wide virtual resources |
| nodes | READ_ONLY | Get overview of cluster node members |
| nodes | READ_ONLY | CPU, memory, uptime, kernel details for node |
| storage | READ_ONLY | List available cluster storage pools |
| storage | READ_ONLY | Query storage volume contents (ISO, backup, disk) |
| storage | READ_ONLY | Disk capacity and usage statistics for pool |
| tasks | READ_ONLY | Query recent cluster background task logs |
| tasks | READ_ONLY | Check completion state for specific UPID |
4. Workflows Domain (workflows)
Tool Name | Scope | Confirm? | Description |
| OPERATOR | No | Provision VM/LXC with automated rollback on step failure |
| OPERATOR | Optional | Perform batch actions (start, stop, reboot) across resource tags |
| OPERATOR | No | Storage pre-check, pre-backup snapshot, vzdump execution, cleanup |
| READ_ONLY | No | Cluster readiness assessment (quorum, disk thresholds, tasks) |
5. Security Domain (security)
Tool Name | Scope | Confirm? | Description |
| READ_ONLY | No | Test client IP against configured CIDR whitelist |
| READ_ONLY | No | Audit current RBAC policy and active security rules |
| READ_ONLY | No | Retrieve high-level runtime security metrics summary |
Resources
Contextual data endpoints read by LLM reasoning engines:
Resource URI | Scope | Description |
| READ_ONLY | Cluster member and total resource summary |
| READ_ONLY | Real-time cluster health and quorum evaluation |
| READ_ONLY | CPU, RAM, and hardware metrics for host node |
| READ_ONLY | Storage pool bindings on specific node |
| READ_ONLY | Storage volume allocation metrics |
| READ_ONLY | Live runtime metrics for virtual machine |
| READ_ONLY | Hardware specification and flags for VM |
| READ_ONLY | Snapshot hierarchy for VM |
| READ_ONLY | Live runtime metrics for LXC container |
| READ_ONLY | Container config parameters |
| READ_ONLY | Snapshot hierarchy for container |
| READ_ONLY | Alias for LXC container status |
| READ_ONLY | Alias for LXC container config |
| READ_ONLY | Alias for LXC container snapshots |
| READ_ONLY | Historical operational logs for Proxmox UPID |
| READ_ONLY | Runtime security engine status |
| READ_ONLY | Active security settings and permission thresholds |
| READ_ONLY | Total audit records count and operation metrics |
Prompts
Interactive user prompt templates guiding complex workflows:
Prompt Name | Target Workflow | Description |
| VM Domain | Step-by-step guided provisioning template for QEMU VM |
| VM Domain | Safety-first guidance for VM snapshot creation and rollback |
| VM Domain | Cloud-Init setup, user creation, and ISO drive binding |
| LXC Domain | Container setup checklist with unprivileged & nesting checks |
| LXC Domain | Diagnostics guide for broken or unstartable containers |
| LXC Domain | Container snapshot lifecycle management checklist |
| Cluster Domain | Comprehensive health, quorum, and network audit guide |
| Node Domain | Host performance tuning and resource saturation checklist |
| Storage Domain | Pool capacity utilization and volume cleanup guide |
| Task Domain | UPID task log parsing and failure root cause analysis |
| Workflows Domain | Decision tree for choosing multi-step workflow routines |
| Workflows Domain | Interactive assistant for multi-tier stack deployments |
| Security Domain | Review active permissions, CIDR rules, and audit logs |
| Security Domain | Verify IP access rights and privilege boundaries |
Security & Audit Architecture
RBAC Permission Enforcement: Every tool execution is validated against the configured
MCP_PERMISSION_LEVEL(read_only,operator,admin).CIDR IP Whitelisting: If
MCP_ALLOWED_CLIENT_IPSis configured, client incoming IP addresses are validated against allowed subnets before processing requests.Destructive Operation Shield: High-risk actions (
delete_vm,stop_vm,remove_disk_vm,rollback_snapshot_vm,delete_container, etc.) require explicitconfirm=trueparameters to prevent accidental execution.Data Scrubbing: All audit payloads and logs are recursively scrubbed to sanitize passwords, tokens, tickets, and secrets (
scrub_payload).Structured Audit Trail: Detailed JSON logs are persisted containing execution timestamp, tool name, client context, parameter payload (scrubbed), execution duration, and Proxmox UPID task references.
Development & Verification
Run the automated quality assurance suite before making contributions:
# 1. Execute Unit & Integration Test Suite
pytest -v
# 2. Run Static Code Linting & Formatting Analysis
ruff check .
# 3. Run Strict Static Type Checking
mypy src testsDocumentation Index
For complete technical specifications, architectural diagrams, and security models, inspect the files in docs/:
License
Distributed under the MIT License. See LICENSE for details.
Available Tools
65 toolsadd_bind_mount_containerB
Add a mount point or bind mount to an LXC container.
Inputs: mp (required), node (required), vmid (required), size, +5 more.
add_vm_diskC
Attach a new virtual disk volume to a VM.
Inputs: node (required), size (required), vmid (required), storage (required), +6 more.
audit_security_rulesA
Fetch current security audit status, CIDR rules, and sensitive key scrubbing configuration.
Inputs: no named parameters. Returns: object
check_client_ipA
Verify whether a given client IP address is allowed by the security policy whitelist.
Inputs: ip_address (required). Returns: object
clone_containerC
Clone an existing LXC container or template.
Inputs: node (required), vmid (required), newid (required), full, +5 more.
clone_vmB
Clone an existing virtual machine or template.
Inputs: node (required), vmid (required), newid (required), full, +3 more.
cluster_healthA
Fetch aggregated health summary, node counts, VM counts, and CPU/memory utilization of the Proxmox cluster.
Inputs: no named parameters.
cluster_resourcesA
Fetch resource list across the Proxmox cluster with optional type filtering (node, qemu, lxc, storage).
Inputs: type_filter.
configure_cloudinit_vmC
Configure Cloud-Init settings for automated OS setup.
Inputs: node (required), vmid (required), citype, ciuser, +8 more.
configure_dns_containerC
Update DNS nameserver and searchdomain settings for an LXC container.
Inputs: node (required), vmid (required), nameserver, searchdomain.
configure_features_containerC
Configure feature flags (nesting, keyctl, fuse) for an LXC container.
Inputs: node (required), vmid (required), fuse, mknod, +3 more.
configure_network_containerC
Configure network adapter settings for an LXC container.
Inputs: node (required), vmid (required), gw, ip, +9 more.
create_containerC
Create a new LXC container. Default unprivileged=True.
Inputs: node (required), ostemplate (required), name, net0, +17 more.
create_snapshot_containerB
Create a snapshot of an LXC container.
Inputs: node (required), vmid (required), snapname (required), description.
create_snapshot_vmC
Create a snapshot of a virtual machine.
Inputs: node (required), vmid (required), snapname (required), vmstate, +1 more.
create_vmC
Create a new QEMU virtual machine on a specified node.
Inputs: name (required), node (required), cpu, bios, +11 more.
delete_containerA
Delete an LXC container and purge resources. DESTRUCTIVE: Requires confirm=True.
Inputs: node (required), vmid (required), confirm, destroy_unreferenced_disks.
delete_snapshot_containerA
Delete an LXC container snapshot. DESTRUCTIVE: Requires confirm=True.
Inputs: node (required), vmid (required), snapname (required), confirm.
delete_snapshot_vmA
Delete a virtual machine snapshot. DESTRUCTIVE: Requires confirm=True.
Inputs: node (required), vmid (required), snapname (required), confirm.
delete_vmA
Delete a QEMU virtual machine and purge resources. DESTRUCTIVE: Requires confirm=True.
Inputs: node (required), vmid (required), purge, confirm.
get_cloudinit_config_vmB
Fetch Cloud-Init configuration settings of a virtual machine.
Inputs: node (required), vmid (required).
get_container_configC
Fetch configuration settings of an LXC container.
Inputs: node (required), vmid (required).
get_container_statusB
Fetch detailed runtime status of an LXC container.
Inputs: node (required), vmid (required).
get_security_summaryA
Retrieve security policy configuration and status summary.
Inputs: no named parameters. Returns: object
get_vm_configC
Fetch configuration settings of a QEMU virtual machine.
Inputs: node (required), vmid (required).
get_vm_statusC
Fetch detailed runtime status of a QEMU virtual machine.
Inputs: node (required), vmid (required).
list_containersA
List all LXC containers on a specified node.
Inputs: node (required).
list_nodesA
List all nodes in the Proxmox cluster with status and resource utilization.
Inputs: no named parameters.
list_snapshots_containerA
List all snapshots for an LXC container.
Inputs: node (required), vmid (required).
list_snapshots_vmB
List all snapshots for a specified virtual machine.
Inputs: node (required), vmid (required).
list_storageA
List storage pools globally or for a specific node, including type, status, and calculated space usage.
Inputs: node.
list_vmsB
List all QEMU virtual machines on a specified node.
Inputs: node (required).
migrate_vmC
Migrate a virtual machine to another node in the cluster.
Inputs: node (required), vmid (required), target (required), online, +2 more.
move_vm_diskB
Move a virtual machine disk to a different storage pool.
Inputs: disk (required), node (required), vmid (required), storage (required), +1 more.
node_statusA
Fetch detailed hardware metrics, CPU/memory usage, kernel version, and status for a specific node.
Inputs: node (required).
pause_vmB
Pause execution of a running QEMU virtual machine.
Inputs: node (required), vmid (required).
reboot_vmC
Reboot a running QEMU virtual machine.
Inputs: node (required), vmid (required), confirm.
recent_tasksB
List recent asynchronous background tasks globally or for a specific node, with optional status and limit filters.
Inputs: node, user, limit, status_filter.
regenerate_cloudinit_vmC
Regenerate the Cloud-Init drive image for a VM.
Inputs: node (required), vmid (required).
remove_bind_mount_containerA
Remove a mount point from an LXC container. DESTRUCTIVE: Requires confirm=True.
Inputs: node (required), vmid (required), mp_key (required), confirm.
resize_container_diskC
Extend rootfs or disk capacity of an LXC container.
Inputs: node (required), vmid (required), disk, size.
resize_vm_diskC
Extend the capacity of a virtual machine disk.
Inputs: disk (required), node (required), size (required), vmid (required).
restart_containerA
Reboot/restart an LXC container. DESTRUCTIVE: Requires confirm=True.
Inputs: node (required), vmid (required), confirm.
resume_vmB
Resume execution of a paused QEMU virtual machine.
Inputs: node (required), vmid (required).
rollback_snapshot_containerA
Rollback LXC container state to a snapshot. DESTRUCTIVE: Requires confirm=True.
Inputs: node (required), vmid (required), snapname (required), confirm.
rollback_snapshot_vmA
Rollback virtual machine state to a snapshot. DESTRUCTIVE: Requires confirm=True.
Inputs: node (required), vmid (required), snapname (required), confirm.
run_backup_flowA
Execute multi-step backup workflow: storage pre-checks, pre-backup snapshotting, vzdump execution, and cleanup.
Inputs: node (required), vmid (required), storage (required), mode, +4 more.
run_bulk_operationA
Execute batch lifecycle actions (start, stop, shutdown, pause, resume) across VMs or LXC containers matching filters.
Inputs: action (required), node, tags, vmids, +3 more.
run_cluster_checkA
Aggregate cluster readiness state including node health, quorum state, storage space, and task health.
Inputs: check_quorum, check_storage, check_node_health, min_free_storage_bytes.
run_provisioning_workflowC
Execute multi-step VM or LXC container provisioning with automated step tracing and failure rollback.
Inputs: name (required), node (required), net0, vmid, +9 more.
shutdown_containerB
Gracefully shutdown an LXC container. DESTRUCTIVE: Requires confirm=True.
Inputs: node (required), vmid (required), confirm, timeout_sec.
shutdown_vmA
Gracefully shutdown a QEMU virtual machine via ACPI signal.
Inputs: node (required), vmid (required).
start_containerA
Start a stopped LXC container.
Inputs: node (required), vmid (required).
start_vmB
Start a stopped QEMU virtual machine.
Inputs: node (required), vmid (required).
stop_containerA
Forcefully stop an LXC container. DESTRUCTIVE: Requires confirm=True.
Inputs: node (required), vmid (required), confirm.
stop_vmA
Forcefully stop (power off) a QEMU virtual machine. DESTRUCTIVE: Requires confirm=True.
Inputs: node (required), vmid (required), confirm.
storage_contentA
List volume items (VM disks, ISOs, LXC templates, backups) inside a storage pool on a node with optional content_type filter.
Inputs: storage (required), node, content_type.
storage_statusA
Fetch capacity, total/used bytes, and detailed status for a specific storage pool on a node.
Inputs: node (required), storage (required).
suspend_vmC
Suspend virtual machine state to disk.
Inputs: node (required), vmid (required), todisk.
task_statusA
Fetch status and exit status of an asynchronous Proxmox background task by UPID.
Inputs: node (required), upid (required).
template_containerB
Convert an LXC container to a reusable template.
Inputs: node (required), vmid (required).
template_vmB
Convert a QEMU virtual machine to a reusable template.
Inputs: node (required), vmid (required).
update_cpu_vmC
Update CPU core and socket allocation of a virtual machine.
Inputs: node (required), vmid (required), cores (required), cpu, +3 more.
update_memory_vmB
Update RAM memory size and ballooning configuration of a VM.
Inputs: node (required), vmid (required), memory (required), hugepages, +1 more.
update_resources_containerC
Update CPU cores, memory, or swap resources of an LXC container.
Inputs: node (required), vmid (required), swap, cores, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 65 tools
Each tool targets a distinct action and resource type (VM, container, storage, cluster, etc.). Overlapping operations like stop_vm vs shutdown_vm vs pause_vm are clearly differentiated by their descriptions, and workflow tools are uniquely named and scoped.
The majority of tools follow a consistent verb_noun pattern (e.g., create_vm, delete_vm, list_snapshots_container). However, several tools deviate with noun-first names like storage_content, task_status, and cluster_health, which mix conventions and slightly reduce predictability.
With 65 tools, this server is extremely heavy and exceeds the typical scope for a single MCP server. Even for a complex domain like Proxmox, the number is overwhelming and would benefit from splitting into smaller, focused servers (e.g., vm_management, container_management, cluster_management).
The tool set provides comprehensive lifecycle coverage for VMs, containers, storage, cluster health, nodes, and security, including create, read, update, delete, snapshots, and operational actions. Workflow tools for provisioning, backup, and cluster checks fill higher-level gaps, leaving few obvious missing operations.
Maintenance
Related MCP Connectors
Deploy, monitor, and manage your OpenClaw AI assistants via natural language.
Manage VeriTeknik servers, DNS, backups and support tickets from your AI assistant.
Manage American Cloud VMs, Kubernetes, databases, storage, networks and DNS from your AI assistant.
Manage Vozora VPS servers, SSH keys, firewalls, DNS and usage from an AI agent.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, and cluster operations via natural language.MIT
- AlicenseCqualityDmaintenanceEnables management of Proxmox VE environments, including VMs, containers, storage, and cluster operations through natural language.7653 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to monitor and manage Proxmox VE infrastructure, including nodes, VMs, containers, storage, backups, and networking, via natural language.1MIT
- AlicenseAqualityBmaintenanceEnables natural language interaction with Proxmox VE clusters for managing VMs, containers, storage, and snapshots.2710 npm3MIT