ProxmoxMCP-Plus v0.6.6

Changes

• Fix #183: default Compose host publications to IPv4 loopback for native MCP HTTP (8000) and OpenAPI (8811). MCP_HTTP_BIND_ADDRESS and OPENAPI_BIND_ADDRESS provide explicit per-mode overrides.
• Put OpenAPI behind the openapi profile; both Compose modes are opt-in. Remove the cross-mode required-variable interpolation so MCP-only deployments no longer need PROXMOX_API_KEY. Application startup continues to enforce the selected mode's authentication.
• Enable no-new-privileges and drop all Linux capabilities on both example services. Verify hardened OpenAPI/native HTTP operation and missing-credential rejection in container CI, with native ARM release health checks under the same capability restrictions.
• Document profile selection, reverse proxies/tunnels, container-network routing, explicit LAN bindings and migration from the previous default OpenAPI service.

Upgrade

Update/rebuild the image and Compose file, set the selected mode's credential, and recreate the wanted service:

docker compose --profile openapi up -d --build --force-recreate proxmox-mcp-api
# Or use the native MCP HTTP mode:
docker compose --profile mcp-http up -d --build --force-recreate proxmox-mcp-http

Plain docker compose up -d now selects no services. Existing containers keep their old configuration until recreated. If migrating to MCP-only mode, explicitly stop an old OpenAPI service with docker compose --profile openapi stop proxmox-mcp-api. The named jobs volume is preserved.

Host-side proxies/tunnels can use loopback. Containerized proxies use the shared Docker network and service DNS. For direct remote access, explicitly set the appropriate bind-address variable; container listeners and the bare image default mode remain unchanged. See Compose deployment.

Install proxmox-mcp-plus==0.6.6 or ghcr.io/rekklesna/proxmoxmcp-plus:0.6.6. Python tool behavior and database schemas are unchanged. No production Proxmox operation is used for validation.