Proxmox MCP Server

Created By
johnstettera year ago
mcp server for interfacing with proxmox
Overview

what is Proxmox MCP Server?

Proxmox MCP Server is a Model Context Protocol (MCP) server designed to interface with a Proxmox VE server, providing infrastructure context to Large Language Models (LLMs).

how to use Proxmox MCP Server?

To use the Proxmox MCP Server, clone the repository, set up your Proxmox credentials in the .env file, and run the server using Docker Compose. The server will be accessible at http://localhost:8008.

key features of Proxmox MCP Server?

  • Retrieve cluster-wide information
  • Query specific node details
  • Get VM information and status
  • List all VMs in the cluster
  • Supports Docker and Docker Compose for easy deployment
  • Secure credential management through environment variables

use cases of Proxmox MCP Server?

  1. Integrating Proxmox infrastructure data with AI applications.
  2. Automating management tasks for virtual machines in a Proxmox cluster.
  3. Providing context-aware responses in applications utilizing LLMs.

FAQ from Proxmox MCP Server?

  • What are the prerequisites for using Proxmox MCP Server?

You need Python 3.11 or higher, Docker, Docker Compose, and access to a Proxmox VE server with API credentials.

  • How do I run the server locally?

You can run the server locally by creating a virtual environment, installing dependencies, and using Uvicorn to run the application.

  • Is there a license for Proxmox MCP Server?

Yes, the project is licensed under the MIT license.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
johnstetter
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)

2 days ago