proxmox-safe-mcp
Related Servers
Alternatives to proxmox-safe-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to inspect and control Proxmox VE clusters through the full API, with optional SSH/LXC command execution, read-only by default and writes gated behind explicit authorization.1MIT
- AlicenseBqualityBmaintenanceEnables schema-validated access to all 680 Proxmox VE API endpoints plus curated guest, snapshot, backup, storage, and task tools, with read-only behavior by default and controlled writes when explicitly enabled.20AGPL 3.0
- AlicenseBqualityBmaintenanceEnables AI assistants to inspect and manage Proxmox VE clusters conversationally, including provisioning VMs and LXC containers, resizing disks, handling snapshots and backups, configuring Cloud-Init and firewall rules, and executing guest commands with mandatory confirmation safeguards.26MIT
- AlicenseNot gradedqualityBmaintenanceEnables management of many Proxmox VE clusters from a single server, exposing read and inventory tools plus guarded destructive operations that follow a plan → approve → apply flow. Per-cluster tokens, fail-closed guest protection with time-boxed waivers, and audit logging keep every action scoped, attributable, and reversible.1MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to diagnose Proxmox VE clusters — quorum and HA state, Ceph and ZFS health, backup coverage audits, task failures, pending updates and node evacuation planning — with answers returned as findings and recommended steps. VM power, snapshot and migration operations are available but disabled by default, requiring a preview and a bound confirmation token before anything executes.1333 PyPIMIT
- FlicenseAqualityDmaintenanceEnables an AI assistant to fully navigate a single-node Proxmox VE host over SSH, with modes for read-only inspection, safe operations, and full control including provisioning and destruction.34-
TDQS
Scored across 5 tools
Each tool targets a distinct aspect of the Proxmox environment: cluster status, node status, guest listing, guest power control, and guest snapshotting. There is no overlap in purposes, making selection unambiguous.
The names mix noun-initial patterns (cluster_status, node_status, guest_power) with verb-initial patterns (list_guests, snapshot_guest). This inconsistency is noticeable but still readable and predictable overall.
With only 5 tools, the server is tightly scoped and each tool serves a clear purpose. This is well-balanced for a specialized MCP server focused on monitoring and safe guest operations.
The set covers status, listing, power, and snapshot operations but lacks lifecycle management (create, update, delete guests). While potentially intentional for a 'safe' server, it leaves notable gaps for full Proxmox administration.