A
licenseNot graded
qualityD
maintenanceA Python-based server enabling interaction with Proxmox hypervisors. It supports secure authentication and provides tools for managing nodes, VMs, clusters, and storage.
289
MIT
Proximo
Related Servers
Alternatives to Proximo
- 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.1,160 PyPI533MIT
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.28 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.14MIT
- FlicenseNot gradedqualityCmaintenanceEnables managing Proxmox Virtual Environment resources including VMs, containers, storage, cluster status, nodes, and tasks.-
- FlicenseBqualityBmaintenanceEnables natural language management of Proxmox VE VMs and containers, including lifecycle, snapshots, cloud-init, and secure multi-step automation workflows.65-
- AlicenseBqualityCmaintenanceEnables AI assistants to manage Proxmox VE infrastructure, including VMs, containers, storage, network, high availability, replication, SDN, and node administration.10016 npmMIT
TDQS
A4.1/5.0
Scored across 7 tools
Disambiguation4/5
Each tool has a distinct role: find/schema/read/call form a discovery-execution pipeline, recall serves estate/memory questions, and audit_entries/audit_verify handle ledger inspection and integrity. The only mild overlap is between proximo_recall and audit_entries for "what changed" questions, and between proximo_read and the broader proximo_call, but the descriptions draw clear lines.
Naming Consistency4/5
Names use consistent snake_case and clear domain prefixes (proximo_ vs audit_), which makes grouping obvious. However, not all names follow a single verb_noun pattern: proximo_tool_schema and audit_entries are noun-style while the rest are verb-led, so it is slightly mixed rather than fully uniform.
Tool Count5/5
Seven exposed tools is appropriate for a facade server: search, schema lookup, read-only execution, general execution, memory recall, and audit read/verify. Each earns its place, and the 908 underlying tools are intentionally indexed behind find_tools instead of being exposed directly.
Completeness4/5
The discovery → schema → execute lifecycle is fully covered, with audit read/verify and estate recall rounding out the domain. A full catalog listing tool is absent, but keyword search plus exact-name calling covers the practical workflow, so there are no serious dead ends.
Maintenance
ActivityActive
ResponsivenessResponsive