# Reported issues for ProxmoxMCP-Plus Pod holds 10 of 10 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user. Back to [ProxmoxMCP-Plus](/mcp/proxmoxmcp-plus). ## Most discussed ### Feature request: optional bearer auth for the native Streamable HTTP /mcp endpoint ## Summary When running in `PROXMOX_MCP_MODE=mcp-http`, the native Streamable HTTP endpoint on `:8000/mcp` accepts **any** request. `PROXMOX_API_KEY` does not apply to it — that key only guards the OpenAPI proxy on `:8811`, and the two modes are mutually exclusive processes, so there is currently no configuration in which `/mcp` is authenticated. Since that endpoint exposes the full tool surface (power management, backups, guest creation/deletion within the token's ACL scope), the only availab [Read the thread](https://github.com/RekklesNA/ProxmoxMCP-Plus/issues/118) · 2026-08-11 · closed · external user · 1 comment ### Feature Request: Whitelist of exposed tools to reduce token spend on local LLM TL:DR: you should add a whitelist.json or environment (or both) to ONLY expose the MCP tools I care about so they are not surfaced to MCP clients, thus reducing the precious tokens the dormant tools take up just by existing. Last night I had an infuriating and token-wasting session only to find out this isn't even a thing; but it should be 🥲 In an effort to reduce tokens on my LOCAL LLMs, I learned that JUST the fact of having MCP tools (enabled), not even USING them, but simply that they exi [Read the thread](https://github.com/RekklesNA/ProxmoxMCP-Plus/issues/102) · 2026-07-01 · open · external user · 3 comments ### Add option to configure DNS rebinding protection for MCP transport ## Problem When deploying ProxmoxMCP-Plus behind a reverse proxy or MCP gateway (e.g. agentgateway), the Python MCP SDK's DNS rebinding protection rejects requests with `421 Misdirected Request` because the incoming `Host` header doesn't match `localhost`. There's currently no way to configure this without patching the SDK at runtime. ## Root Cause In `src/proxmox_mcp/server.py`, the `FastMCP()` constructor is called without a `transport_security` parameter: ```python self.mcp = FastMCP( [Read the thread](https://github.com/RekklesNA/ProxmoxMCP-Plus/issues/92) · 2026-05-18 · closed · external user · 1 comment ### Compatibility: Home Assistant MCP client fails on nested payload schema ($ref/$defs) for get_containersArguments ## Summary ProxmoxMCP-Plus appears to work with permissive MCP clients, but Home Assistant's MCP integration currently fails to load this server because at least one tool schema uses a nested `payload` object via `$ref`/`$defs`. This causes HA to put the MCP config entry into `setup_retry`. ## Observed error in Home Assistant ``` Error converting schema Invalid schema, missing type: {'$defs': {'GetContainersPayload': {'properties': {'node': {'anyOf': [{'type': 'string'}, {'type': 'null'}], 'de [Read the thread](https://github.com/RekklesNA/ProxmoxMCP-Plus/issues/81) · 2026-04-29 · closed · external user · 1 comment ### Missing container command execution setup On previous version I managed to get this to work with your guide. I see now there's been a lot of changes and also this guide is no longer available. Can you help update it? Great MCP btw! [Read the thread](https://github.com/RekklesNA/ProxmoxMCP-Plus/issues/75) · 2026-04-26 · closed · external user · 2 comments ### Feature: Add uvx entry point for direct GitHub installation TITLE: Add uvx entry point for direct GitHub installation DESCRIPTION: ## Summary Add `uvx` entry point support, enabling users to run ProxmoxMCP-Plus directly from GitHub without cloning. ## Changes 1. **pyproject.toml** - Added `[project.scripts]` entry point: ```toml [project.scripts] proxmox-mcp = "proxmox_mcp.server:main" ``` 2. **proxmox-config/opencode/** - OpenCode configuration examples: - `opencode.jsonc.example` - MCP server configuration template - `proxmox-mcp [Read the thread](https://github.com/RekklesNA/ProxmoxMCP-Plus/issues/41) · 2026-03-31 · closed · outside contributor · 1 comment ### Network binding settings in config.json are being ignored (hardcoded to 127.0.0.1, port 8000) Hey, I’ve been trying to get this running in a Docker container/LXC environment so I can point an external agent to it, but I’ve run into an issue where the server ignores the host and port settings defined in the mcp section of the config.json file. **The Issue:** Even if I set mcp.host to 0.0.0.0 and change the port in the config file, the server still binds to 127.0.0.1:8000. This makes the Docker image essentially unreachable from the host or the rest of the network. **Steps to Reproduce: [Read the thread](https://github.com/RekklesNA/ProxmoxMCP-Plus/issues/35) · 2026-03-07 · closed · external user · 1 comment ### Why does /health return {"detail":"Not Found"} when running ProxmoxMCP-Plus in Docker? I've been trying to deploy the ProxmoxMCP-Plus project. I've followed the instructions to set up the API Token (with PVE administrator permissions) and used Docker Compose to spin up the environment. From the `Dockerfile`, the service seems to be running fine on port 8811, but I'm hitting a strange issue: whenever I try to access http://:8811/health or the root path, the API consistently returns {"detail":"Not Found"}. Image at interpreter shutdown, possibly due to daemon threads ``` ## Environment | | | |---|---| | proxmox-mcp-plus | 0.5.12 (als [Read the thread](https://github.com/RekklesNA/ProxmoxMCP-Plus/issues/112) · 2026-07-30 · closed · outside contributor · 0 comments ### Add HTTP Streamable MCP support Currently when running in docker, it's not possible for an MCP client to connect due to the server only support STDIO. This prevent client on other host using the MCP server. Would be great if we can support HTTP mode. [Read the thread](https://github.com/RekklesNA/ProxmoxMCP-Plus/issues/84) · 2026-05-06 · closed · external user · 0 comments The remaining reports are on [the project's issue tracker](https://github.com/RekklesNA/ProxmoxMCP-Plus/issues).