What can proxmox-mcp do?

proxmox ve resource enumeration via mcp protocol, mcp tool schema generation from proxmox api endpoints, credential-based authentication to proxmox api with token support, docker containerized mcp server deployment with single-command startup, read-only access control with optional write capability configuration, mcp protocol compliance and client compatibility

proxmox-mcp

MCP ServerFree

Minimal Proxmox VE MCP server - one Docker command, read-only by default

Open Source

/ 100

6 capabilities

Capabilities6 decomposed

proxmox ve resource enumeration via mcp protocol

Medium confidence

Exposes Proxmox VE infrastructure (nodes, VMs, containers, storage) as MCP tools that Claude and other LLM clients can invoke. Uses the MCP server specification to translate Proxmox REST API responses into structured tool definitions, enabling LLMs to query cluster state without direct API knowledge. Implements read-only access by default with optional credential-based authentication to the Proxmox API endpoint.

Solves for

Query current VM and container status across a Proxmox cluster from ClaudeList available nodes, storage pools, and network resources programmaticallyBuild LLM-driven infrastructure monitoring dashboards that pull live Proxmox stateEnable Claude to understand cluster topology before suggesting operational changes

Best for

DevOps teams integrating Proxmox infrastructure with Claude-based automation

Solo developers building LLM agents that need real-time visibility into hypervisor state

Organizations standardizing on MCP for infrastructure tooling across multiple LLM clients

Requires

Docker or container runtime for MCP server deployment

Proxmox VE 7.0+ with accessible REST API endpoint

Valid Proxmox API token or username/password credentials

Limitations

Read-only by default — no VM creation, deletion, or state modification without explicit configuration

Requires network connectivity to Proxmox API endpoint (typically port 8006)

No built-in caching — each tool invocation queries live Proxmox API, adding ~500ms-2s latency per request

What makes it unique

Minimal Docker-based MCP server that directly wraps Proxmox REST API without intermediate abstraction layers, enabling single-command deployment ('one Docker command') while maintaining read-only safety defaults and MCP protocol compliance

vs alternatives

Simpler deployment and lower operational overhead than building custom Proxmox integrations in Python/Go, and safer by default (read-only) compared to exposing raw Proxmox API to LLMs

mcp tool schema generation from proxmox api endpoints

Medium confidence

Automatically generates MCP tool definitions (name, description, input schema, output schema) by introspecting Proxmox REST API endpoints and translating them into LLM-callable tools. Maps Proxmox API parameters to JSON Schema for input validation and structures responses as typed outputs that Claude can parse and act upon. Handles authentication headers and endpoint routing transparently.

Solves for

Automatically expose new Proxmox API endpoints as Claude tools without manual schema definitionEnsure tool schemas stay synchronized with Proxmox API changesEnable Claude to understand valid parameters and expected outputs for each infrastructure query

Best for

Teams maintaining Proxmox infrastructure who want low-friction LLM integration

Developers building extensible MCP servers that adapt to API changes automatically

Requires

Proxmox VE 7.0+ with documented REST API

MCP server with introspection capabilities

Limitations

Schema generation accuracy depends on Proxmox API documentation completeness

Complex nested Proxmox responses may require manual schema refinement for optimal LLM comprehension

No automatic handling of deprecated Proxmox API endpoints — requires manual tool removal

What makes it unique

Leverages Proxmox API structure to programmatically generate MCP tool schemas rather than requiring manual tool definition, reducing maintenance burden and keeping tool definitions aligned with API versions

vs alternatives

Avoids hand-written tool definitions that drift from API reality, unlike static MCP server implementations that require code changes for each new endpoint

credential-based authentication to proxmox api with token support

Medium confidence

Manages authentication to Proxmox VE REST API using either API tokens (preferred, fine-grained permissions) or username/password credentials. Stores credentials securely (environment variables or config files) and injects them into all outbound Proxmox API requests as Bearer tokens or Basic Auth headers. Validates credentials at server startup and fails fast if authentication fails.

Solves for

Securely authenticate MCP server to Proxmox without embedding credentials in codeUse Proxmox API tokens with minimal required permissions instead of full user accountsRotate credentials without redeploying the MCP server

Best for

Production deployments requiring credential isolation and audit trails

Teams using Proxmox RBAC to limit MCP server permissions to read-only operations

Requires

Proxmox API token or valid user credentials

Environment variable or config file for credential storage

Network access to Proxmox API endpoint

Limitations

Credentials must be provided at server startup — no runtime credential refresh without restart

No built-in credential rotation mechanism — requires external secret management (Vault, K8s Secrets)

Token expiration not automatically handled — expired tokens cause all subsequent API calls to fail

What makes it unique

Supports both Proxmox API tokens (fine-grained, revocable) and legacy username/password auth, with read-only default configuration that prevents accidental infrastructure modifications through the MCP interface

vs alternatives

More secure than embedding credentials in MCP tool definitions, and supports Proxmox's modern token-based auth unlike older integration approaches that rely solely on user accounts

docker containerized mcp server deployment with single-command startup

Medium confidence

Packages the Proxmox MCP server as a Docker image with pre-configured entrypoint, environment variable injection, and network binding. Enables deployment via a single 'docker run' command with credential and endpoint configuration passed as environment variables. Includes health checks and graceful shutdown handling for container orchestration systems.

Solves for

Deploy Proxmox MCP server to any Docker-compatible environment (local, cloud, Kubernetes) in secondsIntegrate MCP server into existing Docker Compose or Kubernetes infrastructure stacksAvoid dependency management and Python/Node.js version conflicts by containerizing the entire runtime

Best for

DevOps teams already using Docker/Kubernetes for infrastructure

Solo developers wanting minimal setup overhead for local testing

Organizations with container registry and orchestration infrastructure

Requires

Docker 20.10+ or compatible container runtime

Network connectivity from container to Proxmox API endpoint

Environment variables for Proxmox credentials and endpoint URL

Limitations

Requires Docker daemon or container runtime — not suitable for bare-metal or serverless deployments

Container image size and startup time add overhead compared to native binary execution

Network isolation in containers may require explicit port mapping and firewall rules

What makes it unique

Advertises 'one Docker command' deployment model, eliminating installation complexity and dependency conflicts by bundling the entire MCP server runtime and Proxmox client libraries into a single container image

vs alternatives

Faster to deploy and more reproducible than manual installation from source, and requires less operational knowledge than building and running the server natively

read-only access control with optional write capability configuration

Medium confidence

Enforces read-only access to Proxmox infrastructure by default, preventing Claude or other LLM clients from accidentally (or maliciously) modifying VMs, containers, or cluster state through MCP tools. Provides configuration option to selectively enable write operations (VM power control, container management) for trusted deployments, with audit logging of all state-modifying operations.

Solves for

Safely expose Proxmox infrastructure to Claude without risk of accidental VM deletion or misconfigurationEnable monitoring and diagnostic queries while preventing operational changesGradually expand LLM permissions from read-only to controlled write operations as trust increases

Best for

Production environments where infrastructure stability is critical

Teams new to LLM-driven infrastructure automation who want safe defaults

Regulated industries requiring audit trails and change control

Requires

Configuration file or environment variable to enable write operations

Proxmox API token with appropriate permissions (read-only or read-write)

Limitations

Read-only mode limits LLM ability to remediate infrastructure issues autonomously

Enabling write operations requires explicit configuration — no granular per-operation permissions

No built-in audit logging — write operations must be logged externally (syslog, CloudWatch, etc.)

What makes it unique

Defaults to read-only access, requiring explicit opt-in for write operations, which is a safer-by-default approach than exposing full API capabilities and relying on LLM judgment to avoid destructive actions

vs alternatives

Prevents accidental infrastructure damage that could occur with unrestricted API access, and provides a clear security boundary that can be audited and enforced at the MCP server level rather than relying on Proxmox RBAC alone

mcp protocol compliance and client compatibility

Medium confidence

Implements the Model Context Protocol (MCP) specification, enabling the Proxmox server to be discovered and invoked by any MCP-compatible client (Claude Desktop, LLM frameworks, custom applications). Handles MCP message serialization/deserialization, tool invocation routing, and response formatting according to the MCP standard. Supports both stdio and HTTP transport modes for flexible client integration.

Solves for

Use Proxmox MCP server with Claude Desktop without custom integration codeIntegrate Proxmox infrastructure queries into LLM frameworks (LangChain, LlamaIndex, etc.)Build custom applications that invoke Proxmox tools through the standard MCP interface

Best for

Teams standardizing on MCP for multi-tool LLM integrations

Developers building LLM agents that need to compose multiple infrastructure and business tools

Organizations with heterogeneous tooling that benefits from a unified MCP interface

Requires

MCP-compatible client (Claude Desktop 0.3.0+, or framework with MCP SDK)

Proper MCP server configuration (stdio or HTTP transport)

Limitations

MCP is a relatively new standard — not all LLM frameworks have mature MCP support yet

Client-side MCP implementation quality varies — some clients may not fully support all MCP features

Transport mode (stdio vs HTTP) must be chosen at deployment time — no runtime switching

What makes it unique

Adheres to the MCP specification, enabling seamless integration with Claude and other MCP-aware clients without requiring custom protocol adapters or client-specific code

vs alternatives

More interoperable than proprietary integration approaches, and enables future compatibility with new MCP clients as the ecosystem grows

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Related Artifactssharing capabilities

Artifacts that share capabilities with proxmox-mcp, ranked by overlap. Discovered automatically through the match graph.

CLI Tool27

mcp-client

** MCP REST API and CLI client for interacting with MCP servers, supports OpenAI, Claude, Gemini, Ollama etc.

authentication and credential management for mcp serversmcp server discovery and capability introspection

2 shared capabilities

MCP Server31

@ivotoby/openapi-mcp-server

An MCP server that exposes OpenAPI endpoints as resources

mcp protocol integration and resource registrationopenapi schema introspection and resource exposure

2 shared capabilities

MCP Server36

klavis

Klavis AI: MCP integration platforms that let AI agents use tools reliably at any scale

rest api for mcp server provisioning and lifecycle managementmulti-service mcp server orchestration with oauth2 authentication

2 shared capabilities

Framework47

mcp-use

The fullstack MCP framework to develop MCP Apps for ChatGPT / Claude & MCP Servers for AI Agents.

mcp protocol schema introspection and capability discoveryauthentication and authorization for mcp server access

2 shared capabilities

MCP Server25

secure-mcp-server

MCP server: secure-mcp-server

authentication and credential management for mcp clients

1 shared capability

MCP Server27

Mastra/mcp

** - Client implementation for Mastra, providing seamless integration with MCP-compatible AI models and tools.

mcp server authentication and credential management

1 shared capability

Best For

✓DevOps teams integrating Proxmox infrastructure with Claude-based automation
✓Solo developers building LLM agents that need real-time visibility into hypervisor state
✓Organizations standardizing on MCP for infrastructure tooling across multiple LLM clients
✓Teams maintaining Proxmox infrastructure who want low-friction LLM integration
✓Developers building extensible MCP servers that adapt to API changes automatically
✓Production deployments requiring credential isolation and audit trails
✓Teams using Proxmox RBAC to limit MCP server permissions to read-only operations
✓DevOps teams already using Docker/Kubernetes for infrastructure

Known Limitations

⚠Read-only by default — no VM creation, deletion, or state modification without explicit configuration
⚠Requires network connectivity to Proxmox API endpoint (typically port 8006)
⚠No built-in caching — each tool invocation queries live Proxmox API, adding ~500ms-2s latency per request
⚠Single-cluster support per MCP server instance — separate deployments needed for multi-cluster environments
⚠Schema generation accuracy depends on Proxmox API documentation completeness
⚠Complex nested Proxmox responses may require manual schema refinement for optimal LLM comprehension

Requirements

Docker or container runtime for MCP server deploymentProxmox VE 7.0+ with accessible REST API endpointValid Proxmox API token or username/password credentialsMCP-compatible client (Claude Desktop, LLM frameworks with MCP support)Proxmox VE 7.0+ with documented REST APIMCP server with introspection capabilitiesProxmox API token or valid user credentialsEnvironment variable or config file for credential storage

Input / Output

Accepts: MCP tool invocation parameters (node names, VM IDs, resource filters), Proxmox API credentials (token or basic auth), Proxmox API endpoint definitions, API token string or username/password pair, Docker run command with environment variables, Configuration flag (boolean) to enable/disable write operations, MCP protocol messages (JSON-RPC format)

Produces: structured JSON containing VM/container metadata (name, status, CPU, memory, uptime), node inventory with resource utilization metrics, storage pool information and capacity data, JSON Schema tool definitions compatible with MCP specification, Bearer token or Basic Auth header for Proxmox API requests, Running MCP server listening on configured port (default 8000 or similar), MCP tool set filtered to read-only or read-write based on configuration, MCP protocol responses with tool results (JSON-RPC format)

UnfragileRank

Adoption5%(25% weight)

Quality12%(25% weight)

Ecosystem59%(15% weight)

Match Graph25%(30% weight)

Freshness75%(5% weight)

UnfragileRank is computed from adoption signals, documentation quality, ecosystem connectivity, match graph feedback, and freshness. No artifact can pay for a higher rank.

Type: MCP Server

6 capabilities

Visit proxmox-mcp→

About

Minimal Proxmox VE MCP server - one Docker command, read-only by default

Alternatives to proxmox-mcp

Supabase69Platform

Search the Supabase docs for up-to-date guidance and troubleshoot errors quickly. Manage organizations, projects, databases, and Edge Functions, including migrations, SQL, logs, advisors, keys, and type generation, in one flow. Create and manage development branches to iterate safely, confirm costs

Compare →

Tavily MCP Server62MCP Server

AI-optimized web search and content extraction via Tavily MCP.

Compare →

MongoDB MCP Server62MCP Server

Query and manage MongoDB databases and collections via MCP.

Compare →

Firecrawl MCP Server62MCP Server

Scrape websites and extract structured data via Firecrawl MCP.

Compare →

Are you the builder of proxmox-mcp?

Claim this artifact to get a verified badge, access match analytics, see which intents users search for, and manage your listing.

Claim this artifact →Verification via email

Get the weekly brief

New tools, rising stars, and what's actually worth your time. No spam.

Data Sources

smithery

Looking for something else?

Search →

Capabilities6 decomposed

proxmox ve resource enumeration via mcp protocol

Medium confidence

Solves for

Best for

DevOps teams integrating Proxmox infrastructure with Claude-based automation

Solo developers building LLM agents that need real-time visibility into hypervisor state

Organizations standardizing on MCP for infrastructure tooling across multiple LLM clients

Requires

Docker or container runtime for MCP server deployment

Proxmox VE 7.0+ with accessible REST API endpoint

Valid Proxmox API token or username/password credentials

Limitations

Read-only by default — no VM creation, deletion, or state modification without explicit configuration

Requires network connectivity to Proxmox API endpoint (typically port 8006)

No built-in caching — each tool invocation queries live Proxmox API, adding ~500ms-2s latency per request

What makes it unique

vs alternatives

Simpler deployment and lower operational overhead than building custom Proxmox integrations in Python/Go, and safer by default (read-only) compared to exposing raw Proxmox API to LLMs

mcp tool schema generation from proxmox api endpoints

Medium confidence

Solves for

Best for

Teams maintaining Proxmox infrastructure who want low-friction LLM integration

Developers building extensible MCP servers that adapt to API changes automatically

Requires

Proxmox VE 7.0+ with documented REST API

MCP server with introspection capabilities

Limitations

Schema generation accuracy depends on Proxmox API documentation completeness

Complex nested Proxmox responses may require manual schema refinement for optimal LLM comprehension

No automatic handling of deprecated Proxmox API endpoints — requires manual tool removal

What makes it unique

vs alternatives

Avoids hand-written tool definitions that drift from API reality, unlike static MCP server implementations that require code changes for each new endpoint

credential-based authentication to proxmox api with token support

Medium confidence

Solves for

Best for

Production deployments requiring credential isolation and audit trails

Teams using Proxmox RBAC to limit MCP server permissions to read-only operations

Requires

Proxmox API token or valid user credentials

Environment variable or config file for credential storage

Network access to Proxmox API endpoint

Limitations

Credentials must be provided at server startup — no runtime credential refresh without restart

No built-in credential rotation mechanism — requires external secret management (Vault, K8s Secrets)

Token expiration not automatically handled — expired tokens cause all subsequent API calls to fail

What makes it unique

vs alternatives

More secure than embedding credentials in MCP tool definitions, and supports Proxmox's modern token-based auth unlike older integration approaches that rely solely on user accounts

docker containerized mcp server deployment with single-command startup

Medium confidence

Solves for

Best for

DevOps teams already using Docker/Kubernetes for infrastructure

Solo developers wanting minimal setup overhead for local testing

Organizations with container registry and orchestration infrastructure

Requires

Docker 20.10+ or compatible container runtime

Network connectivity from container to Proxmox API endpoint

Environment variables for Proxmox credentials and endpoint URL

Limitations

Requires Docker daemon or container runtime — not suitable for bare-metal or serverless deployments

Container image size and startup time add overhead compared to native binary execution

Network isolation in containers may require explicit port mapping and firewall rules

What makes it unique

vs alternatives

Faster to deploy and more reproducible than manual installation from source, and requires less operational knowledge than building and running the server natively

read-only access control with optional write capability configuration

Medium confidence

Solves for

Best for

Production environments where infrastructure stability is critical

Teams new to LLM-driven infrastructure automation who want safe defaults

Regulated industries requiring audit trails and change control

Requires

Configuration file or environment variable to enable write operations

Proxmox API token with appropriate permissions (read-only or read-write)

Limitations

Read-only mode limits LLM ability to remediate infrastructure issues autonomously

Enabling write operations requires explicit configuration — no granular per-operation permissions

No built-in audit logging — write operations must be logged externally (syslog, CloudWatch, etc.)

What makes it unique

vs alternatives

mcp protocol compliance and client compatibility

Medium confidence

Solves for

Best for

Teams standardizing on MCP for multi-tool LLM integrations

Developers building LLM agents that need to compose multiple infrastructure and business tools

Organizations with heterogeneous tooling that benefits from a unified MCP interface

Requires

MCP-compatible client (Claude Desktop 0.3.0+, or framework with MCP SDK)

Proper MCP server configuration (stdio or HTTP transport)

Limitations

MCP is a relatively new standard — not all LLM frameworks have mature MCP support yet

Client-side MCP implementation quality varies — some clients may not fully support all MCP features

Transport mode (stdio vs HTTP) must be chosen at deployment time — no runtime switching

What makes it unique

Adheres to the MCP specification, enabling seamless integration with Claude and other MCP-aware clients without requiring custom protocol adapters or client-specific code

vs alternatives

More interoperable than proprietary integration approaches, and enables future compatibility with new MCP clients as the ecosystem grows

Capabilities are decomposed by AI analysis. Each maps to specific user intents and improves with match feedback.

Alternatives to proxmox-mcp

Supabase69Platform

Compare →

Tavily MCP Server62MCP Server

AI-optimized web search and content extraction via Tavily MCP.

Compare →

MongoDB MCP Server62MCP Server

Query and manage MongoDB databases and collections via MCP.

Compare →

Firecrawl MCP Server62MCP Server

Scrape websites and extract structured data via Firecrawl MCP.

Compare →

proxmox-mcp

Capabilities6 decomposed

proxmox ve resource enumeration via mcp protocol

mcp tool schema generation from proxmox api endpoints

credential-based authentication to proxmox api with token support

docker containerized mcp server deployment with single-command startup

read-only access control with optional write capability configuration

mcp protocol compliance and client compatibility

Related Artifactssharing capabilities

mcp-client

@ivotoby/openapi-mcp-server

klavis

mcp-use

secure-mcp-server

Mastra/mcp

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to proxmox-mcp

Are you the builder of proxmox-mcp?

Get the weekly brief

Data Sources

proxmox-mcp

Capabilities6 decomposed

proxmox ve resource enumeration via mcp protocol

mcp tool schema generation from proxmox api endpoints

credential-based authentication to proxmox api with token support

docker containerized mcp server deployment with single-command startup

read-only access control with optional write capability configuration

mcp protocol compliance and client compatibility

Related Artifactssharing capabilities

mcp-client

@ivotoby/openapi-mcp-server

klavis

mcp-use

secure-mcp-server

Mastra/mcp

Best For

Known Limitations

Requirements

Input / Output

UnfragileRank

About

Categories

Alternatives to proxmox-mcp

Are you the builder of proxmox-mcp?

Get the weekly brief

Data Sources