Proxmox VE

io.github.akmalovaa/proxmox-mcpv2.3.0Docker & Containers

Manage Proxmox VE nodes, VMs, containers, storage and snapshots. Read-only by default.

The current version, v2.3.0, was published to the official MCP registry on 2026-09-01. It is distributed as proxmox-ve-mcp on PyPI and as the Docker image ghcr.io/akmalovaa/proxmox-mcp:2.3.0, filed under Docker & Containers by this index, and declares 19 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Proxmox VE in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire

Auditable install path →Watch it hold a drift →

Trust verdict · v1 advisory · method

REVIEWstatus: PARTIALfresh until 2026-10-25 00:08 UTC

screened 2026-09-01tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“Normal capability description”via static_description

Limits of this verdict

- Semantic screen only - the deterministic conformance probe has not run on this server
- Confidence is reported but not yet calibrated (v1)
- Screen reads the tool description, not the live behavior
- advisory
- registry description only no input schema
- screen model 8b
- Still current: the description we screened is unchanged, re-checked against the registry
- The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.

That verdict was true at screening time (snapshot 2026-10-18).

Contracts can change after screening, with no version bump. The gate pins Proxmox VE’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown

[Independent trust record for Proxmox VE](https://mcpindex.ai/server/io-github-akmalovaa-proxmox-mcp) - screening verdict, registry provenance, and contract drift monitoring.

HTML

<a href="https://mcpindex.ai/server/io-github-akmalovaa-proxmox-mcp">Independent trust record for Proxmox VE</a> - screening verdict, registry provenance, and contract drift monitoring.

Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown

[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-akmalovaa-proxmox-mcp)](https://mcpindex.ai/server/io-github-akmalovaa-proxmox-mcp)

HTML

<a href="https://mcpindex.ai/server/io-github-akmalovaa-proxmox-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-akmalovaa-proxmox-mcp" alt="mcpindex verdict" height="20" /></a>

Environment variables

PROXMOX_HOST

required

Proxmox host IP or hostname.

PROXMOX_PORT

Proxmox API port.

PROXMOX_VERIFY_SSL

Verify the TLS certificate. Proxmox self-signs by default.

PROXMOX_TIMEOUT

Seconds to wait for each Proxmox API request.

PROXMOX_USER

API user, including the realm.

PROXMOX_TOKEN_NAME

API token name. Use this plus PROXMOX_TOKEN_VALUE, or PROXMOX_PASSWORD.

PROXMOX_TOKEN_VALUE

secret

API token secret.

PROXMOX_PASSWORD

secret

Password, used only when no API token is set.

PROXMOX_RISK_LEVEL

Which tools exist: read-only, plus lifecycle, or everything.

PROXMOX_TOOLS_ALLOW

Comma-separated tool names to register, intersected with the risk level. Unset = all of them.

PROXMOX_REDACT_SECRETS

Mask cipassword and sshkeys in every response.

PROXMOX_MCP_TRANSPORT

stdio (default) or streamable-http.

PROXMOX_MCP_HOST

HTTP bind address. Anything but loopback also needs PROXMOX_MCP_ALLOWED_HOSTS.

PROXMOX_MCP_PORT

HTTP port.

PROXMOX_MCP_PATH

Streamable HTTP endpoint path.

PROXMOX_MCP_JSON_RESPONSE

Answer with JSON instead of an SSE stream.

PROXMOX_MCP_ALLOWED_HOSTS

Comma-separated Host headers to accept over HTTP; '*' disables the check.

PROXMOX_MCP_ALLOWED_ORIGINS

Comma-separated browser origins allowed to call the endpoint. Empty = same-origin only.

SENTRY_DSN

secret

Optional: report tool traces and errors to Sentry. Unset disables it.

PROXMOX_HOST

required

Proxmox host IP or hostname.

PROXMOX_PORT

Proxmox API port.

PROXMOX_VERIFY_SSL

Verify the TLS certificate. Proxmox self-signs by default.

PROXMOX_TIMEOUT

Seconds to wait for each Proxmox API request.

PROXMOX_USER

API user, including the realm.

PROXMOX_TOKEN_NAME

API token name. Use this plus PROXMOX_TOKEN_VALUE, or PROXMOX_PASSWORD.

PROXMOX_TOKEN_VALUE

secret

API token secret.

PROXMOX_PASSWORD

secret

Password, used only when no API token is set.

PROXMOX_RISK_LEVEL

Which tools exist: read-only, plus lifecycle, or everything.

PROXMOX_TOOLS_ALLOW

Comma-separated tool names to register, intersected with the risk level. Unset = all of them.

PROXMOX_REDACT_SECRETS

Mask cipassword and sshkeys in every response.

PROXMOX_MCP_TRANSPORT

stdio (default) or streamable-http.

PROXMOX_MCP_HOST

HTTP bind address. Anything but loopback also needs PROXMOX_MCP_ALLOWED_HOSTS.

PROXMOX_MCP_PORT

HTTP port.

PROXMOX_MCP_PATH

Streamable HTTP endpoint path.

PROXMOX_MCP_JSON_RESPONSE

Answer with JSON instead of an SSE stream.

PROXMOX_MCP_ALLOWED_HOSTS

Comma-separated Host headers to accept over HTTP; '*' disables the check.

PROXMOX_MCP_ALLOWED_ORIGINS

Comma-separated browser origins allowed to call the endpoint. Empty = same-origin only.

SENTRY_DSN

secret

Optional: report tool traces and errors to Sentry. Unset disables it.

MCP quality score · maturity, not trust · methodology

freshness

completeness

installability

documentation

stability

Alternatives in Docker & Containers

Scalingo MCP by usefulapi

io.usefulapi/scalingo

Manage Scalingo PaaS apps, deployments, containers, logs and env vars from your AI assistant.

Terminal49

io.github.Terminal49/terminal49

Find and monitor ocean shipments and containers, and create new tracking requests.

io.github.alisaitteke/docker-mcp

MCP server for managing Docker containers, images, networks, volumes, and registries

Install this server

Claude Desktop (uvx)

{
  "mcpServers": {
    "proxmox-mcp": {
      "command": "uvx",
      "args": [
        "--",
        "proxmox-ve-mcp"
      ],
      "env": {
        "PROXMOX_HOST": "<proxmox_host>",
        "PROXMOX_PORT": "8006",
        "PROXMOX_VERIFY_SSL": "false",
        "PROXMOX_TIMEOUT": "15",
        "PROXMOX_USER": "root@pam",
        "PROXMOX_TOKEN_NAME": "<proxmox_token_name>",
        "PROXMOX_TOKEN_VALUE": "<your-proxmox_token_value>",
        "PROXMOX_PASSWORD": "<your-proxmox_password>",
        "PROXMOX_RISK_LEVEL": "read",
        "PROXMOX_TOOLS_ALLOW": "<proxmox_tools_allow>",
        "PROXMOX_REDACT_SECRETS": "true",
        "PROXMOX_MCP_TRANSPORT": "stdio",
        "PROXMOX_MCP_HOST": "127.0.0.1",
        "PROXMOX_MCP_PORT": "8000",
        "PROXMOX_MCP_PATH": "/mcp",
        "PROXMOX_MCP_JSON_RESPONSE": "true",
        "PROXMOX_MCP_ALLOWED_HOSTS": "<proxmox_mcp_allowed_hosts>",
        "PROXMOX_MCP_ALLOWED_ORIGINS": "<proxmox_mcp_allowed_origins>",
        "SENTRY_DSN": "<your-sentry_dsn>"
      }
    }
  }
}

Claude Desktop (Docker)

{
  "mcpServers": {
    "proxmox-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "--",
        "ghcr.io/akmalovaa/proxmox-mcp:2.3.0"
      ],
      "env": {
        "PROXMOX_HOST": "<proxmox_host>",
        "PROXMOX_PORT": "8006",
        "PROXMOX_VERIFY_SSL": "false",
        "PROXMOX_TIMEOUT": "15",
        "PROXMOX_USER": "root@pam",
        "PROXMOX_TOKEN_NAME": "<proxmox_token_name>",
        "PROXMOX_TOKEN_VALUE": "<your-proxmox_token_value>",
        "PROXMOX_PASSWORD": "<your-proxmox_password>",
        "PROXMOX_RISK_LEVEL": "read",
        "PROXMOX_TOOLS_ALLOW": "<proxmox_tools_allow>",
        "PROXMOX_REDACT_SECRETS": "true",
        "PROXMOX_MCP_TRANSPORT": "stdio",
        "PROXMOX_MCP_HOST": "127.0.0.1",
        "PROXMOX_MCP_PORT": "8000",
        "PROXMOX_MCP_PATH": "/mcp",
        "PROXMOX_MCP_JSON_RESPONSE": "true",
        "PROXMOX_MCP_ALLOWED_HOSTS": "<proxmox_mcp_allowed_hosts>",
        "PROXMOX_MCP_ALLOWED_ORIGINS": "<proxmox_mcp_allowed_origins>",
        "SENTRY_DSN": "<your-sentry_dsn>"
      }
    }
  }
}

Verdict API

curl -s mcpindex.ai/api/v1/trust/server/io-github-akmalovaa-proxmox-mcp

Free-tier verdict as JSON: decision + dimensions + severity. Call it from your agent before it invokes a tool it just discovered.

Details

version: v2.3.0
category: Docker & Containers
verdict expires: 2026-10-25
quality: 99 / 100
operator: akmalovaa

Listing

Listed from the official MCP registry. Unclaimed by its maintainer. Maintainer? Email us →

Provenance

Each verdict is bound to a hash of the exact description it judged, so a re-crawl that changes the text produces a new record rather than silently inheriting this one. Verdict history is hash-chained and anchored to Bitcoin via OpenTimestamps (latest confirmed at block 971,808). Verify it yourself.

Links

Repository →Website →