ProxmoxMCP-Plus, a community MCP server for Proxmox VE

• Lists every virtual machine with its status and resource use

  Shows all VMs across your Proxmox cluster, whether each is running, and how much CPU and memory it uses.

  Try: “Which VMs are running right now and how much memory is each using?”

  Read · get_vms

• Lists your LXC containers, optionally on one node, with their status

  Shows the LXC containers across the cluster or on one node, with status and optional resource stats.

  Try: “List all containers on node pve1 and show which are stopped.”

  Read · get_containers

• Lists the nodes in your cluster with status, CPU and memory

  Shows each Proxmox node, whether it is online, and its CPU and memory use.

  Try: “Show me all my Proxmox nodes and how loaded they are.”

  Read · get_nodes

• Shows detailed status for one node

  Gives detailed CPU, memory and status figures for a single Proxmox node.

  Try: “How is node pve1 doing right now?”

  Read · get_node_status

• Shows overall cluster health and quorum

  Reports the health and configuration of the whole Proxmox cluster, including quorum.

  Try: “Is my cluster healthy and does it have quorum?”

  Read · get_cluster_status

• Lists storage pools with usage across the cluster

  Shows every storage pool in the cluster, how full it is and how it is configured.

  Try: “Which storage pools are almost full?”

  Read · get_storage

• Shows storage capacity on one node

  Shows how much space each storage has on a specific node, optionally for one storage ID.

  Try: “How much free space is left on local-lvm on pve2?”

  Read · get_node_storage

• Shows a VM's full hardware and boot settings

  Returns a VM's configuration: CPU, memory, disks, network, BIOS and boot order.

  Try: “Show me the config of VM 101.”

  Read · get_vm_config

• Shows a container's full configuration

  Returns an LXC container's configuration, such as cores, memory, disks and network.

  Try: “What are the network settings of container 200?”

  Read · get_container_config

• Finds a running VM's IP addresses

  Reads a running VM's network interfaces and IP addresses through the QEMU guest agent.

  Try: “What IP did VM 105 get?”

  Read · get_vm_ip_addresses

• Finds a running container's IP addresses

  Returns the current IP addresses of a running LXC container.

  Try: “What is the IP address of container 210?”

  Read · get_container_ip

• Lists the snapshots of a VM or container

  Shows all snapshots taken of a given VM or container.

  Try: “What snapshots exist for VM 101?”

  Read · list_snapshots

• Lists backups, filtered by node, storage or VM

  Shows the backups available across the cluster, optionally for one node, storage or VM ID.

  Try: “When was VM 101 last backed up?”

  Read · list_backups

• Lists ISO images you can install from

  Shows the installer ISO images stored in your cluster, optionally on one node or storage.

  Try: “Which ISOs do I have available?”

  Read · list_isos

• Lists OS templates for new containers

  Shows the OS templates you can use to create LXC containers.

  Try: “Which Debian container templates can I use?”

  Read · list_templates

• Lists network bridges on a node

  Shows the network bridges and VNets on a node that VMs and containers can attach to.

  Try: “Which network bridges are on pve1?”

  Read · list_bridges

• Finds the next free VM or container ID

  Returns the next unused ID in the cluster, handy before creating or cloning a machine.

  Try: “What's the next free VM ID?”

  Read · get_next_vmid

• Reads a node's system log

  Reads system log entries from a Proxmox node, with optional time range and service filter.

  Try: “Show the last 100 syslog lines from pve1 about pveproxy.”

  Read · get_node_syslog

• Reads the log of a Proxmox task

  Shows the output of a specific Proxmox task, such as a backup or VM start.

  Try: “Why did the last backup task on pve1 fail?”

  Read · get_task_log

• Reads recent cluster-wide log entries

  Shows the most recent log entries for the whole cluster.

  Try: “What happened in the cluster in the last hour?”

  Read · get_cluster_log

• Reads a node's firewall log

  Shows the host firewall log of a Proxmox node.

  Try: “Show blocked connections in pve1's firewall log today.”

  Read · get_node_firewall_log

• Reads the firewall log of a VM or container

  Shows the firewall log for a specific VM or container.

  Try: “Show the firewall log for container 200.”

  Read · get_guest_firewall_log

• Shows CPU, I/O wait, memory, disk and network metrics for a node

  Reads recent performance metrics for one node to help find what is slowing it down. It does not run commands.

  Try: “Why is pve1 slow? Check its I/O wait and memory.”

  Read · get_node_diagnostics

• Checks a node's clock and timezone

  Reads a node's time and timezone to spot clock drift that breaks Proxmox logins.

  Try: “Is the clock on pve2 out of sync?”

  Read · get_node_time

• Shows public cluster join details and fingerprints

  Returns the public information needed to join a node to the cluster, without credentials.

  Try: “Give me the join information for my cluster.”

  Read · get_cluster_join_info

• Checks whether a VM can be moved to another node

  Assesses if a stopped VM can be migrated offline to another node, checking storage, bridges and HA. It moves nothing.

  Try: “Can VM 110 be migrated to pve2?”

  Read · preflight_vm_migration

• Checks whether a container can be moved to another node

  Assesses if a container can be migrated, checking storage, space, mounts, HA and backups. It moves nothing.

  Try: “Check whether container 220 can move to pve3.”

  Read · preflight_container_migration

• Creates a new virtual machine

  Creates a VM with the CPU, memory, disk, storage and network you specify, optionally booting from an ISO.

  Try: “Create a VM called test-web with 2 CPUs, 4 GB RAM and a 32 GB disk on pve1.”

  Write · create_vm

• Copies an existing VM or template into a new VM

  Clones a VM or template, fully or linked, into a new VM ID, optionally on another node.

  Try: “Clone template 9000 into a new VM 120 named k8s-node-1.”

  Write · clone_vm

• Creates a new LXC container from a template

  Creates a container from an OS template with the cores, memory, disk and network you choose.

  Try: “Create a Debian 12 container with 1 core and 512 MB RAM on pve1.”

  Write · create_container

• Starts a virtual machine

  Powers on a VM.

  Try: “Start VM 105.”

  Write · start_vm

• Starts one or more containers

  Starts the LXC containers you name.

  Try: “Start container 200 and 201.”

  Write · start_container

• Shuts a VM down cleanly

  Asks the VM's operating system to shut down gracefully.

  Try: “Shut down VM 105 cleanly.”

  Write · shutdown_vm

• Force-stops a virtual machine

  Stops a VM immediately, like pulling the power. Use shutdown for a clean stop.

  Try: “Force stop VM 105, it's frozen.”

  Write · stop_vm

• Stops one or more containers

  Stops LXC containers, gracefully by default or by force.

  Try: “Stop container 200.”

  Write · stop_container

• Hard-restarts a virtual machine

  Resets a VM, restarting it without a clean shutdown.

  Try: “Reset VM 105.”

  Write · reset_vm

• Reboots one or more containers

  Restarts the LXC containers you name.

  Try: “Reboot container 210.”

  Write · restart_container

• Changes a VM's size, cloud-init, ISO, boot order or bridge

  Updates an existing VM's memory, cores, cloud-init user and SSH keys, IP settings, ISO media, boot order or network bridge. Treated as high risk.

  Try: “Give VM 120 8 GB of RAM and add my SSH key via cloud-init.”

  Write · update_vm_config

• Changes a container's cores, memory, swap or disk size

  Adjusts CPU, memory and swap, or grows a container's disk. Each disk call adds space again.

  Try: “Give container 200 2 cores and grow its disk by 8 GB.”

  Write · update_container_resources

• Changes a container's IP, gateway or bridge

  Edits the network settings of a container's interface. This can cut its connection.

  Try: “Set container 200 to IP 192.168.1.50/24 with gateway 192.168.1.1.”

  Write · update_container_network

• Replaces a VM's notes

  Sets the description shown in the Notes field for a VM.

  Try: “Set VM 105's notes to 'Nextcloud, owner: Sam'.”

  Write · set_vm_description

• Replaces a container's notes

  Sets the description shown in the Notes field for a container.

  Try: “Add a note to container 200 saying it runs Pi-hole.”

  Write · set_container_description

• Takes a snapshot of a VM or container

  Saves the current state of a VM or container so you can roll back later.

  Try: “Snapshot VM 101 as before-upgrade.”

  Write · create_snapshot

• Rolls a VM or container back to a snapshot

  Restores a VM or container to an earlier snapshot, discarding changes since then.

  Try: “Roll VM 101 back to before-upgrade.”

  Write · rollback_snapshot

• Backs up a VM or container to storage

  Creates a backup on the storage you choose. Stop or suspend modes can interrupt the guest.

  Try: “Back up VM 101 to backup-nfs with zstd.”

  Write · create_backup

• Restores a backup into a new VM or container

  Restores a backup archive into a new ID; it does not overwrite the original.

  Try: “Restore last night's backup of VM 101 as VM 151.”

  Write · restore_backup

• Downloads an ISO image to Proxmox storage

  Has Proxmox download an installer ISO from a URL into storage, optionally checking its checksum.

  Try: “Download the Ubuntu 24.04 server ISO to local storage.”

  Write · download_iso

• Downloads a container template from an HTTPS URL

  Has Proxmox download an LXC template archive into template storage.

  Try: “Download this Alpine container template to local.”

  Write · download_template

• Attaches an uploaded cloud image as a VM disk

  Imports a disk image already in import storage into an empty disk slot on a stopped VM.

  Try: “Import debian-12.qcow2 into VM 130's scsi1.”

  Write · import_cloud_image

• Sets up a serial console on a stopped VM

  Adds a serial socket and switches the VM's display to serial, for console access.

  Try: “Enable a serial console on VM 130.”

  Write · configure_vm_serial_console

• Moves a stopped VM to another node

  Submits an offline migration of a stopped VM after checks and your explicit confirmations. High risk.

  Try: “Migrate stopped VM 110 to pve2.”

  Write · migrate_vm

• Moves a container to another node

  Submits a container migration after fresh checks, with downtime confirmation for running containers. High risk.

  Try: “Move container 220 to pve3, restart allowed.”

  Write · migrate_container

• Deletes a virtual machine completely

  Removes a VM and its disks; purge also removes HA, backup job and replication references.

  Try: “Delete VM 199, it was only a test.”

  Delete · delete_vm

• Deletes one or more containers completely

  Removes LXC containers and their disks.

  Try: “Delete container 299.”

  Delete · delete_container

• Deletes a snapshot

  Removes a snapshot from a VM or container.

  Try: “Delete the before-upgrade snapshot on VM 101.”

  Delete · delete_snapshot

• Deletes a backup file

  Removes a backup volume from storage.

  Try: “Delete the oldest backup of VM 101.”

  Delete · delete_backup

• Deletes an ISO or template from storage

  Removes an ISO image or template file from storage.

  Try: “Delete the old Debian 11 ISO.”

  Delete · delete_iso

• Runs a command inside a running VM

  Runs a command in a VM through the QEMU guest agent, subject to your command policy.

  Try: “Run 'df -h' inside VM 105.”

  Runs code · execute_vm_command

• Runs a shell command inside a running container

  Runs a command in an LXC container over SSH to the Proxmox node. Only appears if you add SSH settings.

  Try: “Run 'apt list --upgradable' in container 200.”

  Runs code · execute_container_command

• Runs an allowed command on a Proxmox host

  Runs a command on a physical Proxmox node over SSH, only if you enable it and it matches your allowlist.

  Try: “Run uptime on pve1.”

  Runs code · execute_node_command

• Adds or replaces root SSH keys in a container

  Writes SSH authorized keys for root in a container, over SSH to the node. High risk.

  Try: “Add my public key to container 200.”

  Write · update_container_ssh_keys

• Used by the assistant behind the scenes

  Lists the Proxmox environments it is set up to manage

  Shows configured Proxmox targets, their reachability and node names, without credentials.

  Try: “Which Proxmox targets can you reach?”

  Read · list_targets

• Lists tracked long-running jobs

  Shows the background jobs, such as backups or VM creation, that it is tracking.

  Try: “Which jobs are still running?”

  Read · list_jobs

• Shows the state of one tracked job

  Returns the status, progress and result of a tracked job.

  Try: “Is the backup job finished?”

  Read · get_job

• Refreshes a tracked job's status from Proxmox

  Checks Proxmox for the latest progress of a tracked job.

  Try: “Check on the VM clone job again.”

  Read · poll_job

• Cancels a running job

  Tries to cancel a long-running Proxmox task it is tracking.

  Try: “Cancel the ISO download.”

  Write · cancel_job

• Retries a failed job

  Runs a failed tracked job again with the same settings.

  Try: “Retry the failed backup job.”

  Write · retry_job

• Settles a job whose outcome was uncertain

  Records the real outcome of a job whose submission was uncertain, after you check Proxmox's task history.

  Try: “Mark that uncertain migration job as not submitted.”

  Write · reconcile_job

Watch out for

• It can stop, delete and roll back VMs

  With a broad token the assistant can delete VMs, containers, snapshots and backups or force-stop guests. Give it a token limited to what you need, or use read-only mode. github.com

• Approval checks are off by default

  Risky operations are only logged unless you switch the high-risk policy to enforce and set an approval token. Do that before using it on machines you care about. github.com

• SSH command tools reach the Proxmox host

  Container and node command tools appear only if you add SSH settings, and their command filter is not a sandbox. Leave SSH out unless you need it. github.com

• The examples use the root account

  The sample config uses root@pam. Create a separate Proxmox user and token with only the privileges you need. github.com

• The HTTP mode needs a key

  The Docker HTTP mode will not start without a key and listens only on your own machine unless you change it. github.com

Security advisories

In their words