MCP server for Proxmox VE infrastructure management
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"proxmox-mcp-server-2","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Proxmox MCP Server ## Overview This is a Model Context Protocol (MCP) server that provides tools for interacting with Proxmox VE infrastructure. It enables AI assistants and other MCP clients to manage virtual machines, containers, storage, networking, firewall rules, high availability, and more through a standardized interface. The server supports both API token and password-based authentication against local and remote Proxmox instances. ## Distributions - PyPI - https://pypi.org/project/proxmox-mcp-server/ - Docker - https://hub.docker.com/r/mcp/proxmox ## Tools ### Node Management - **`list_nodes`** - List all nodes in the Proxmox cluster with their status, CPU, memory, and uptime - **`get_node_status`** - Get detailed status of a specific node including CPU, memory, disk, uptime, and kernel info - **`get_node_config`** - Get the configuration of a node (description, wakeonlan, etc.) - **`get_node_dns`** - Get DNS settings for a node - **`get_node_network`** - Get network interface configuration for a node - **`get_node_network_interface`** - Get details for a specific network interface - **`create_node_network_interface`** - Create a network interface on a node - **`list_node_services`** - List all system services on a node (pve, ssh, cron, etc.) - **`manage_node_service`** - Start, stop, restart, or reload a system service on a node - **`get_node_syslog`** - Read system log (syslog) entries from a node - **`get_node_journal`** - Read systemd journal entries from a node - **`list_node_tasks`** - List recent tasks on a node - **`get_task_status`** - Get the status of a specific task by its UPID - **`get_task_log`** - Get log output of a specific task - **`stop_task`** - Stop (abort) a running task - **`get_node_time`** - Get the current time and timezone of a node - **`get_node_subscription`** - Get subscription status for a node - **`get_node_apt_update`** - List available package updates on a node - **`run_apt_update`** - Refresh the package index …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.