Proximo
Related Servers
Alternatives to Proximo
- AlicenseNot gradedqualityFmaintenanceA Python-based server enabling interaction with Proxmox hypervisors. It supports secure authentication and provides tools for managing nodes, VMs, clusters, and storage.295MIT
- AlicenseNot gradedqualityAmaintenanceAn enhanced Python-based MCP server that enables complete VM lifecycle management and monitoring of Proxmox virtualization platforms through natural language, with 11 REST API endpoints for seamless integration.3,619 PyPI613MIT
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables comprehensive management of Proxmox Virtual Environment through 35 tools for VMs, containers, storage, backups, snapshots, and cluster operations via the Proxmox VE API.24 npm22MIT
- FlicenseNot gradedqualityDmaintenanceEnables management of Proxmox VE environments via the Proxmox API, including node listing, guest management, and VM/LXC creation with Cloud-Init.-
- AlicenseNot gradedqualityCmaintenanceEnables comprehensive management of Proxmox virtualization environments, including VM and container lifecycle, snapshots, backups, monitoring, and OpenAPI integration.12MIT
- FlicenseNot gradedqualityCmaintenanceEnables managing Proxmox Virtual Environment resources including VMs, containers, storage, cluster status, nodes, and tasks.-
- AlicenseNot gradedqualityAmaintenanceExposes 338 tools for the Proxmox Virtual Environment API, enabling users to inspect and control nodes, QEMU VMs, LXC containers, storage and backups, clustering and HA, users and permissions, firewall rules, disks, Ceph, ACME certificates, SDN, notifications, and resource pools. Includes lifecycle actions, snapshots, migration, metrics, task tracking, and guest-agent command execution, with an optional read-only mode that blocks all writes.MIT
- FlicenseBqualityDmaintenanceEnables natural language management of Proxmox VE VMs and containers, including lifecycle, snapshots, cloud-init, and secure multi-step automation workflows.65-
TDQS
Scored across 6 tools
The four Proximo tools have reasonably distinct roles: find discovers addresses, plan previews/verdicts a specific address, read executes GETs, and call performs governed mutations. There is some conceptual overlap between plan and read because plan includes a governed read of the target, but the descriptions clarify when each should be used.
All names are snake_case and readable, and the core API tools consistently use the proximo_ prefix with action verbs. The audit tools use a separate audit_ prefix and noun-style names, which is a minor convention split rather than a major inconsistency.
Six tools is well-scoped for a governed API gateway: discovery, planning, read, mutation, and two audit operations. Each tool appears to earn its place without redundant surface area.
The surface covers the main lifecycle: discovering addresses, planning changes, executing reads and mutations, undoing via receipts, and reading/verifying the audit ledger. Minor gaps around explicit arm/status administration may exist, but core governed API workflows are covered.