🚀 Proxmox MCP Server (Node.js Edition)

Created By
gilby125a year ago
MCP server for Proxmox virtualization management with configurable permissions
Overview

What is Proxmox MCP Server?

Proxmox MCP Server is a Node.js-based Model Context Protocol (MCP) server designed for managing Proxmox hypervisors, allowing users to interact with nodes, virtual machines (VMs), and containers through a clean interface with configurable permission levels.

How to use Proxmox MCP Server?

To use the Proxmox MCP Server, clone the repository from GitHub, install the necessary dependencies, and configure your Proxmox API token in a .env file. You can then run the server and interact with it using various MCP tools.

Key features of Proxmox MCP Server?

  • Configurable permission levels for secure operations
  • Comprehensive management of nodes and VMs
  • Real-time resource monitoring
  • Secure token-based authentication
  • Error handling and graceful degradation

Use cases of Proxmox MCP Server?

  1. Managing Proxmox clusters and monitoring node status
  2. Executing commands on VMs securely
  3. Listing and managing virtual machines and containers

FAQ from Proxmox MCP Server?

  • What are the permission levels?

    There are two permission levels: Basic Mode for minimal operations and Elevated Mode for advanced features requiring full permissions.

  • Is it necessary to have a Proxmox server?

    Yes, you need access to a Proxmox server with API token credentials to use this server.

  • Can I run it without Node.js?

    No, Node.js is required to run the Proxmox MCP Server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gilby125
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago