PVEHub-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PVEHUB_TRANSPORT | No | Set to stdio to use the stdio transport instead of HTTP. Stdio mode starts no listener and uses no bearer token. | |
| PVEHUB_ALLOWED_HOSTS | No | Hostnames clients use, including the port if non-default, to avoid 421 Invalid Host header or DNS-rebinding errors. | |
| PVEHUB_MCP_AUTH_TOKEN | No | Bearer token required for the HTTP transport. The HTTP transport refuses to start without this token unless PVEHUB_MCP_AUTH_REQUIRED=false is set for a loopback development setup. | |
| PVEHUB_MCP_AUTH_REQUIRED | No | Set to false to explicitly opt out of the bearer token requirement for loopback development setups only. A non-loopback bind without a token is refused even with this opt-out. | true |
| PVEHUB_AUDIT_INCLUDE_RESULTS | No | Set to true to include result bodies in the audit JSONL log at /data/audit.jsonl. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo recent community issues