Skip to content

ProxmoxMCP-Plus v0.5.13

Latest
Latest

Choose a tag to compare

View all tags
@RekklesNA RekklesNA released this 10 Aug 13:33
v0.5.13
d0b6522
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

ProxmoxMCP-Plus v0.5.13

Release date: 2026-08-10

Read-only log inspection

This release adds five read-only MCP tools for investigating Proxmox nodes, tasks, cluster events, and firewall activity without leaving the MCP client:

  • get_node_syslog
  • get_task_log
  • get_cluster_log
  • get_node_firewall_log
  • get_guest_firewall_log for QEMU VMs and LXC containers

All five tools use Proxmox GET endpoints and do not change cluster state. Access remains subject to Proxmox permissions. Depending on the requested log and its owner, the configured user or API token may need Sys.Syslog, Sys.Audit, or VM.Console on the relevant cluster, node, or guest path. Firewall logging must also be enabled for traffic entries to appear.

Logs can contain usernames, task identifiers, IP addresses, service names, and other sensitive operational details. Grant only the permissions needed and avoid sharing returned logs without review.

Thanks to DevLeti for contributing the inspection tools in PR #116.

Reliable STDIO shutdown

STDIO servers now exit cleanly when they receive SIGINT or SIGTERM, avoiding the CPython _enter_buffered_busy abort that could occur while an MCP SDK reader thread still owned the shared standard-input buffer. Application resources are closed before the process exits, and the shutdown path deliberately avoids high-level standard-stream flushing that could deadlock behind an SDK writer.

SSE and Streamable HTTP retain their existing graceful SystemExit behavior. Thanks to scottrus for diagnosing and contributing the original fix in PR #113.

Compatibility

  • No configuration migration is required.
  • Existing tools, schemas, ports, and transport configuration remain compatible.
  • The new inspection tools are additive and read-only.
  • MCP clients that cache tool definitions may need to reconnect or refresh their tool list after upgrading.

Validation

The release quality gate covers Python 3.11 and 3.12 tests with coverage enforcement, Ruff, Mypy, CodeQL, dependency auditing, package builds, Twine metadata validation, runtime-to-manifest parity, and multi-architecture container publication checks.

Upgrade and rollback

  • Upgrade normally from PyPI, GHCR, or source, then reconnect the MCP client if the new tools are not immediately visible.
  • No application, Docker, or Proxmox configuration change is required solely for this release.
  • To roll back, pin PyPI or source installs to 0.5.12, or use the GHCR tag 0.5.12.
Assets 2
Loading