{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_akmalovaa-proxmox-mcp","slug":"akmalovaa-proxmox-mcp","name":"proxmox-mcp","type":"mcp","url":"https://smithery.ai/servers/akmalovaa/proxmox-mcp","page_url":"https://unfragile.ai/akmalovaa-proxmox-mcp","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:akmalovaa/proxmox-mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_akmalovaa-proxmox-mcp__cap_0","uri":"capability://tool.use.integration.proxmox.ve.resource.enumeration.via.mcp.protocol","name":"proxmox ve resource enumeration via mcp protocol","description":"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.","intents":["Query current VM and container status across a Proxmox cluster from Claude","List available nodes, storage pools, and network resources programmatically","Build LLM-driven infrastructure monitoring dashboards that pull live Proxmox state","Enable 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"],"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"],"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","MCP-compatible client (Claude Desktop, LLM frameworks with MCP support)"],"input_types":["MCP tool invocation parameters (node names, VM IDs, resource filters)","Proxmox API credentials (token or basic auth)"],"output_types":["structured JSON containing VM/container metadata (name, status, CPU, memory, uptime)","node inventory with resource utilization metrics","storage pool information and capacity data"],"categories":["tool-use-integration","infrastructure-monitoring"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_akmalovaa-proxmox-mcp__cap_1","uri":"capability://tool.use.integration.mcp.tool.schema.generation.from.proxmox.api.endpoints","name":"mcp tool schema generation from proxmox api endpoints","description":"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.","intents":["Automatically expose new Proxmox API endpoints as Claude tools without manual schema definition","Ensure tool schemas stay synchronized with Proxmox API changes","Enable 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"],"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"],"requires":["Proxmox VE 7.0+ with documented REST API","MCP server with introspection capabilities"],"input_types":["Proxmox API endpoint definitions"],"output_types":["JSON Schema tool definitions compatible with MCP specification"],"categories":["tool-use-integration","code-generation-editing"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_akmalovaa-proxmox-mcp__cap_2","uri":"capability://tool.use.integration.credential.based.authentication.to.proxmox.api.with.token.support","name":"credential-based authentication to proxmox api with token support","description":"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.","intents":["Securely authenticate MCP server to Proxmox without embedding credentials in code","Use Proxmox API tokens with minimal required permissions instead of full user accounts","Rotate 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"],"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"],"requires":["Proxmox API token or valid user credentials","Environment variable or config file for credential storage","Network access to Proxmox API endpoint"],"input_types":["API token string or username/password pair"],"output_types":["Bearer token or Basic Auth header for Proxmox API requests"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_akmalovaa-proxmox-mcp__cap_3","uri":"capability://automation.workflow.docker.containerized.mcp.server.deployment.with.single.command.startup","name":"docker containerized mcp server deployment with single-command startup","description":"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.","intents":["Deploy Proxmox MCP server to any Docker-compatible environment (local, cloud, Kubernetes) in seconds","Integrate MCP server into existing Docker Compose or Kubernetes infrastructure stacks","Avoid 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"],"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"],"requires":["Docker 20.10+ or compatible container runtime","Network connectivity from container to Proxmox API endpoint","Environment variables for Proxmox credentials and endpoint URL"],"input_types":["Docker run command with environment variables"],"output_types":["Running MCP server listening on configured port (default 8000 or similar)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_akmalovaa-proxmox-mcp__cap_4","uri":"capability://safety.moderation.read.only.access.control.with.optional.write.capability.configuration","name":"read-only access control with optional write capability configuration","description":"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.","intents":["Safely expose Proxmox infrastructure to Claude without risk of accidental VM deletion or misconfiguration","Enable monitoring and diagnostic queries while preventing operational changes","Gradually 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"],"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.)"],"requires":["Configuration file or environment variable to enable write operations","Proxmox API token with appropriate permissions (read-only or read-write)"],"input_types":["Configuration flag (boolean) to enable/disable write operations"],"output_types":["MCP tool set filtered to read-only or read-write based on configuration"],"categories":["safety-moderation","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_akmalovaa-proxmox-mcp__cap_5","uri":"capability://tool.use.integration.mcp.protocol.compliance.and.client.compatibility","name":"mcp protocol compliance and client compatibility","description":"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.","intents":["Use Proxmox MCP server with Claude Desktop without custom integration code","Integrate 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"],"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"],"requires":["MCP-compatible client (Claude Desktop 0.3.0+, or framework with MCP SDK)","Proper MCP server configuration (stdio or HTTP transport)"],"input_types":["MCP protocol messages (JSON-RPC format)"],"output_types":["MCP protocol responses with tool results (JSON-RPC format)"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":24,"verified":false,"data_access_risk":"high","permissions":["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","MCP-compatible client (Claude Desktop, LLM frameworks with MCP support)","Proxmox VE 7.0+ with documented REST API","MCP server with introspection capabilities","Proxmox API token or valid user credentials","Environment variable or config file for credential storage","Network access to Proxmox API endpoint","Docker 20.10+ or compatible container runtime"],"failure_modes":["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","No automatic handling of deprecated Proxmox API endpoints — requires manual tool removal","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","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.22,"ecosystem":0.38999999999999996,"match_graph":0.25,"freshness":0.5,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-05-24T12:16:25.635Z","last_scraped_at":"2026-05-03T15:18:54.202Z","last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=akmalovaa-proxmox-mcp","compare_url":"https://unfragile.ai/compare?artifact=akmalovaa-proxmox-mcp"}},"signature":"PlaHIYIHsrdejtda8WxVuhL8rKD3geB7P0E5XGiraGdFZj2fmlbAxSc0rv6udssu7FCh+4Tt0pik3WsG2NwaCw==","signedAt":"2026-06-22T16:08:19.586Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/akmalovaa-proxmox-mcp","artifact":"https://unfragile.ai/akmalovaa-proxmox-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=akmalovaa-proxmox-mcp","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}