Infrastructure · native api
Proxmox Control
Control VM/container start, stop, status, and deploy workflows through future Proxmox MCP/API integrations.
Native API placeholder
Native API access is safer and more reliable than embedding the Proxmox UI for privileged infrastructure actions.
This page will become an MCP/API-backed control panel with auditable actions, scoped credentials, and clear approval boundaries before privileged operations run.
- Status
- planned
- Launch target
- /apps/proxmox
- Ownership
- Owned or operator-controlled
- Required credentials / permissions
- Proxmox API token, VM/container inventory, Scoped start/stop/deploy permissions
Planned action model
- Read current state through the service API or MCP server.
- Show proposed changes before executing start, stop, deploy, purge, mailbox, DNS, or admin actions.
- Require least-privilege credentials stored outside the repository.
- Log action results for Garza OS and IceWarp operators.