ProxmoxMCP-Plus v0.5.17

Release date: 2026-09-16

VM provisioning tools — #127

Three new tools complete the cloud-init VM provisioning workflow:

• get_next_vmid returns the next available VM/container ID in the selected cluster.
• update_vm_config updates supplied sizing, name, tags and cloud-init settings,
  including SSH public keys, user, IP configuration and DNS settings. SSH keys
  are percent-encoded for the Proxmox API and are not echoed in the result.
• get_vm_ip_addresses returns guest network interfaces and addresses through
  QEMU Guest Agent, plus the first non-loopback IPv4 address as primary_ip.

Each tool supports named targets and tool exposure filters. The two read-only
helpers remain available on read-only targets. VM ID lookup does not reserve an
ID; concurrent provisioning can still require retrying with another available ID.

Safety and permissions

update_vm_config follows the selected target's high-risk operation policy and
accepts approval_token. It is included in the default high-risk operations list.
If you maintain a custom list, add update_vm_config to protect configuration
changes. The existing audit-only default remains unchanged; read-only targets
always reject configuration updates, even with a valid approval token.

Configuration updates no longer require a preliminary VM.Audit read: the API
token needs the configuration privileges required by the fields being changed.
Guest Agent authentication and permission errors remain visible instead of being
misreported as an unavailable agent.

Upgrade and rollback

Install proxmox-mcp-plus==0.5.17 or pull
ghcr.io/rekklesna/proxmoxmcp-plus:0.5.17, then restart the server and reconnect
clients to refresh tool discovery. Existing allowlists must include the new tools
if you want to expose them. No database migration is required.

For cloud-init provisioning, use a prepared cloud-init template; IP discovery
requires a running VM with QEMU Guest Agent enabled and installed. Cloud-init
settings are intended for the next guest boot.

Rolling back to 0.5.16 removes these three tools. Remove their names from explicit
tool exposure lists before rolling back; VM changes already made are not undone.

Validation

PR #127 passed GitHub CI on Python 3.11 and 3.12: 407 tests passed, one live
integration test skipped, and coverage was 80.62%. Ruff, mypy, package validation,
dependency auditing and CodeQL passed. Regression tests cover approval rejection
and acceptance, target isolation, read-only behavior, write-only configuration
permissions and preservation of Guest Agent errors. Maintainer validation used
mocked Proxmox APIs, not a live Proxmox host.

Thanks to @pofallon for the original provisioning implementation.