proxmoxer-mcp-server

MCP server that exposes Proxmox (virtualization) management capabilities to an AI agent via the Model Context Protocol, enabling tool-based actions against a Proxmox host/cluster.

Evaluated Apr 04, 2026 (27d ago)
Homepage ↗ Repo ↗ Infrastructure mcp proxmox virtualization infrastructure-automation agent-tools devops
⚙ Agent Friendliness
44
/ 100
Can an agent use this?
🔒 Security
47
/ 100
Is it safe for agents?
⚡ Reliability
31
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
55
Documentation
45
Error Messages
0
Auth Simplicity
45
Rate Limits
20

🔒 Security

TLS Enforcement
50
Auth Strength
55
Scope Granularity
30
Dep. Hygiene
50
Secret Handling
50

Security posture depends heavily on how the MCP server handles Proxmox connection/auth and whether it enforces least-privilege permissions. No repository-specific evidence was provided here to confirm TLS requirement, secret redaction, dependency CVE status, or authorization scoping.

⚡ Reliability

Uptime/SLA
0
Version Stability
45
Breaking Changes
45
Error Recovery
35
AF Security Reliability

Best When

You want an AI agent to orchestrate Proxmox administrative tasks through a standardized MCP tool interface.

Avoid When

You cannot securely handle Proxmox credentials (API tokens/passwords) or cannot constrain the agent’s permissions and scope.

Use Cases

  • • Agent-driven VM/LXC lifecycle management (create/start/stop/restart/delete)
  • • Automated infrastructure operations and playbooks for Proxmox
  • • ChatOps-style incident response on Proxmox resources (power cycling, status checks)

Not For

  • • Unattended operations without proper credentials/audit controls
  • • Workloads that require strict “read-only” guarantees (unless server is configured to enforce it)
  • • Production-grade change management without approval gates

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: Proxmox authentication (e.g., API token or user credentials)
OAuth: No Scopes: No

Auth mechanisms and scope granularity depend on how the MCP server is implemented/configured; no evidence provided here of OAuth/scopes support.

Pricing

Free tier: No
Requires CC: No

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • ⚠ Proxmox operations may be non-idempotent (e.g., create/delete actions); agents should guard with pre-checks
  • ⚠ Long-running Proxmox tasks may require polling/waiting; agents should handle timeouts carefully
  • ⚠ Credential misconfiguration can cause repeated failures; ensure errors are surfaced clearly and safely

Alternatives

Direct Proxmox API/REST calls using an SDK or custom client Terraform/Ansible providers for Proxmox for repeatable infrastructure changes Other MCP servers tailored to virtualization/infra operations (if available)

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for proxmoxer-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo
API endpoint ↗ Agent guide ↗ Report inaccuracy

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
♥
Community Powered