{"slug": "proxmox-mcp-access", "title": "Proxmox MCP Access", "summary": "A homelab operator running Ollama on an AMD RX 6700 XT 12GB with Open WebUI in a separate Linux VM found that IBM Granite 4.1:8B used a Proxmox MCP connection far more reliably than Qwen3.5:4B/9B, which struggled with tool selection, ran Tool Search slowly, and hallucinated a running Debian VM that did not exist. Granite 4.1:8B was faster, correctly queried Proxmox, reported actual VM and container inventories, checked CPU/RAM/storage resources, and assessed whether the host could accommodate a new VM, though some calculations and technical details needed correcting. The operator's next experiment is granting Granite restricted write access to create a VM through MCP, with dry-run validation and human approval.", "body_md": "**My adventures with local AI, Ollama, Open WebUI and Proxmox MCP**\n\nI’ve been experimenting with using a local LLM to monitor and eventually manage my Proxmox homelab through MCP.\n\nMy setup:\n\nAMD RX 6700 XT 12GB running Ollama on Windows\n\nOpen WebUI running in a separate Linux VM\n\nProxmox MCP connected to a dedicated test host\n\nQwen3.5:4B / 9B and IBM Granite 4.1:8B\n\nGetting everything connected was fairly straightforward, but getting the models to actually use the tools reliably was another story!\n\nQwen struggled with tool selection, especially when Open WebUI’s built-in tools were enabled. Tool Search was painfully slow, and I even had Qwen hallucinate a running Debian VM that didn’t exist. Responses were also surprisingly slow despite 100% GPU offloading.\n\nThen I tried **IBM Granite 4.1:8B**, and things improved dramatically.\n\nGranite was faster, correctly queried Proxmox, reported actual VM/container inventories, checked CPU/RAM/storage resources, and even investigated whether the host could accommodate a new VM.\n\nIt’s not perfect — some calculations and technical details needed correcting — but it’s easily been my best experience so far.\n\n**Next experiment:** Giving Granite restricted write access so it can actually create a VM through MCP, with dry-run validation and human approval.\n\nIt’s been a surprisingly fun rabbit hole, and a good reminder that choosing the right model matters just as much as the hardware!", "url": "https://wpnews.pro/news/proxmox-mcp-access", "canonical_source": "https://forum.level1techs.com/t/proxmox-mcp-access/259451#post_1", "published_at": "2026-10-25 02:47:56+00:00", "updated_at": "2026-10-25 03:11:19.369272+00:00", "lang": "en", "topics": ["ai-agents", "agent-protocols", "ai-tools", "large-language-models", "artificial-intelligence"], "entities": ["Proxmox", "Ollama", "Open WebUI", "IBM", "Granite 4.1:8B", "Qwen3.5", "AMD RX 6700 XT", "MCP"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/proxmox-mcp-access", "markdown": "https://wpnews.pro/news/proxmox-mcp-access.md", "text": "https://wpnews.pro/news/proxmox-mcp-access.txt", "jsonld": "https://wpnews.pro/news/proxmox-mcp-access.jsonld"}}