Skip to main content
Glama
734,453 tools. Updated 2026-11-02 03:24

"Self-hosted MCP server on Proxmox LXC container accessible remotely from AI clients" matching MCP tools:

  • List all QEMU VMs and LXC containers on a Proxmox node for a given inventory instance, helping AI agents inspect infrastructure without raw SSH.
    MIT
  • Create new LXC containers on Proxmox nodes with customizable CPU, memory, swap, storage, and OS templates, plus SSH keys and start options.
    MIT
  • Set up Behavioral-Gate GitHub Actions by generating self-hosted runner prerequisites, workflow YAML using edgegate-bg, and gh secret commands for edge-AI regression on real devices.
    MIT
  • Change configuration of a Proxmox VE VM or LXC container using a dictionary of config values. Hotpluggable changes apply instantly; others are pending until restart.
    MIT

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    MCP server for integrating self-hosted Sentry with AI assistants, enabling project and issue listing, issue details with stack traces, and event retrieval.
    7
    13 npm
    1
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    An MCP server protected by Cloudflare Access as a self-hosted application, validating Access JWT and conditionally exposing tools based on user identity.
    -

Matching MCP Connectors

  • Engineering log of self-hosted AI on NVIDIA DGX Spark (GB10/SM121A). 60+ articles indexed.

  • Send a thought, get one metathought that makes your agent inspect its own assumptions. Keyless.

  • Delete a Proxmox VM or container permanently. Requires confirm=true to destroy the guest and disks irreversibly, with optional purge from jobs and HA.
    MIT
    Destructive
  • List all Plausible sites accessible via your API key, including their timezones. Returns guidance if the Sites API is disabled for self-hosted instances.
    MIT
  • Start a QEMU VM or LXC container on a Proxmox node with confirmation (confirm: true). Returns a task UPID for async tracking, not a completion status.
    MIT
  • Force-stop (hard power-off) a QEMU VM or LXC container on a Proxmox node. Requires confirm: true; returns a task UPID for async tracking.
    MIT
  • Retrieve all VMs and LXC containers across Proxmox nodes with status, node placement, and resource allocation details including CPU, memory, and disk.
    MIT
  • Retrieve hardware specifications, configuration settings, and current runtime status for a specific Proxmox VM or container by ID.
    MIT
  • Gracefully shut down an LXC container on a Proxmox node. Specify the node and container ID; optionally set a timeout in seconds for forced shutdown if graceful fails.
    MIT
  • List all VMs and containers across the cluster, returning details like ID, name, node, type, status, and usage. Optionally filter by type to show only QEMU VMs or LXC containers.
    MIT
  • Migrate a VM or container to another Proxmox node, with live migration for running QEMU VMs and restart migration for LXC containers.
    MIT