Unofficial Proxmox MCP Server

    1

    Full conversational Proxmox VE hypervisor management for Claude Code, Gemini CLI, and Cursor with two-step destruction safety gates.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Unofficial Proxmox MCP Server

    Example session with this skill installed

    List all VMs on the 'pve-01' node and tell me which ones are currently stopped.

    • Read your context and instructions
    • Compiled the unofficial proxmox mcp

    I have queried the pve-01 node for all registered virtual machines and filtered them by their current status.

    Proxmox VM Status Report: pve-01

    VMIDNameStatusCPU UsageMemory UsageUptime
    100docker-prodrunning12.5%4.2GB / 8GB14d 2h
    101home-assistantrunning2.1%1.1GB / 2GB45d 12h
    102media-serverstopped0%0GB / 16GB0s
    105test-ubuntustopped0%0GB / 2GB0s
    110postgres-dbrunning5.8%6.1GB / 8GB3d 18h
    120backup-nodestopped0%0GB / 4GB0s

    Summary of Stopped VMs:

    • media-server (102): Offline. Last backup was completed 24 hours ago.
    • test-ubuntu (105): Offline. Marked for decommissioning.
    • backup-node (120): Offline. Set to manual start only.

    Next steps

    1. Run start_vm for ID 102 if the media services are required.
    2. Check the configuration of ID 105 to verify if it can be safely removed from storage.
    3. Review the task logs for node pve-01 if any of these stopped unexpectedly.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Managing Proxmox Virtual Environment via an LLM often fails due to missing context on node states, storage availability, and VM IDs. This skill provides the bridge to control your homelab or enterprise virtualization cluster using Model Context Protocol (MCP) commands.

    What it does

    • Cluster Monitoring retrieve status updates for nodes, storage pools, and virtual machines.
    • VM Lifecycle Management start, stop, shutdown, and reboot virtual machines or containers.
    • Resource Inventory list all active and inactive guest systems across the entire cluster.
    • Configuration Retrieval pull specific hardware and network configurations for individual IDs.

    How it works

    1. Connect the agent to your Proxmox VE API via an MCP server implementation.
    2. Query the cluster state by asking for a list of nodes or specific VM statuses.
    3. Execute power commands or configuration changes by providing the target VMID.
    4. Verify the task completion by checking the node task logs or updated guest status.

    Frameworks & tools

    This skill works with the Proxmox VE API and requires a configured MCP server (like the Proxmox MCP implementation) running in your environment.

    Why this beats prompting it yourself

    Generic prompts do not know your VMIDs, node names, or current resource locks. This skill provides the structured command interface necessary to interact with the Proxmox API without manual data entry or copy-pasting terminal output.

    Use cases

    • Check which nodes have the lowest memory pressure before deploying a new VM.
    • Bulk restart all virtual machines tagged with a specific service name.
    • Audit storage usage across local-lvm and network-attached storage pools.
    • Troubleshoot a non-responsive guest by checking its current power state and config.

    Known limitations

    Requires an active MCP server connection to a Proxmox host. Cannot perform initial Proxmox installation or physical hardware troubleshooting.

    Requires a running Proxmox MCP server and API access. Limited to operations supported by the underlying MCP implementation.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 6 days ago

    Requires

    Unofficial Proxmox MCP
    Python

    Permissions

    Environment Variables
    Network Access
    Terminal / Shell
    Read Files
    Write Files

    Network Access connects to Proxmox VE REST API over HTTPS. Environment Variables configure PVE host address and auth tokens. Read/Write files and Terminal access support local configs, QEMU guest agent execution, and Terraform IaC exports.

    Listed7 days ago

    What's inside

    Frequently Asked Questions

    This skill uses the Model Context Protocol (MCP) to bridge your LLM with the Proxmox VE API, allowing the agent to see real-time node data and execute VM power commands without you needing to manually copy-paste IDs or terminal outputs.

    Yes, the skill is designed for cluster-wide visibility, enabling you to monitor resource pressure across multiple nodes and manage VMs regardless of which specific host they are currently residing on.

    You will need an active Proxmox VE API user/token and a running MCP server implementation; this skill provides the logic and command structure for your AI agent to communicate with that server.

    This skill is compatible with any AI agent or platform that supports the Model Context Protocol (MCP), such as Claude Desktop or specialized IDE-based AI agents.

    The skill supports core lifecycle tasks including starting, stopping, shutting down, and rebooting both Virtual Machines (VMs) and Linux Containers (LXCs).

    While the skill can retrieve configuration details and manage power states, it cannot perform initial Proxmox ISO installations or resolve physical hardware failures that require manual intervention.

    New in LLM Ops