ProxmoxMCP-Plus v0.5.16

Release date: 2026-09-12

Fix standalone cluster status — #125

get_cluster_status now reports n/a (not clustered) for the cluster name
and quorum on standalone Proxmox VE nodes, instead of using the node name
and incorrectly reporting Quorum: NOT OK.

Cluster metadata is selected by record type, independently of response order.
Real clustered quorum verdicts remain OK or NOT OK, including one-node
clusters. Missing/null quorum information and empty responses report unknown.
Cached responses preserve the same distinction, and API failures remain errors.

No configuration changes or new tools are required.

Upgrade

Install proxmox-mcp-plus==0.5.16 or pull
ghcr.io/rekklesna/proxmoxmcp-plus:0.5.16, then restart the server.
Rolling back to 0.5.15 requires no configuration migration but restores the
standalone quorum reporting bug.

Validation

Regression coverage includes standalone nodes, reordered records, healthy and
non-quorate clusters, missing data, cached output, API failures, and MCP tool calls.
Local validation passed 374 tests with two platform/live-integration skips and
80.38% coverage. Live Proxmox infrastructure was not used in these tests.