Skip to main content
Glama
188,635 tools. Last updated 2026-06-10 12:27

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

  • Create a new Proxmox LXC container with custom resources, OS template, and optional SSH keys. Specify node, ID, hostname, memory, cores, and storage.
    MIT
  • Return the managed ltm platform dashboard URL so the agent can present it to the user. Errors when configured for a self-hosted server.
    Apache 2.0
  • Runs diagnostic checks on the QGIS MCP stack, reporting version, plugin match, processing providers, connected clients, and project status to identify issues.
    GPL 2.0
  • Retrieve quota and rate-limit details for your current plan via the hosted API. Self-hosted deployments receive a clear error.
    MIT
  • Retrieve all VMs and LXC containers across Proxmox nodes with status, node placement, and resource allocation details including CPU, memory, and disk.
    MIT

Matching MCP Servers

Matching MCP Connectors

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

  • Hosted SEO MCP server for URL + keyword scans, entity coverage, competitor gaps, and internal-link opportunities for AI agents.

  • 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
  • Retrieve chain tip information from a self-hosted litecoind node to verify Litecoin blockchain state without relying on third-party indexers.
    Business Source 1.1
  • Retrieve hardware specifications, configuration settings, and current runtime status for a specific Proxmox VM or container by ID.
    MIT
  • Reboot a specified LXC container on a Proxmox node by providing the node name and container ID. Requires lifecycle risk level permissions.
    MIT
  • Closes the active SSH connection to a specified server, allowing automatic reconnection on next command.
    MIT
  • Discover your accessible wallets, policies, capabilities, and AI-ready prompt. Call this first to understand your environment and what you can do.
    MIT
  • Retrieve the full configuration of an LXC container including rootfs, network, resource limits, and hostname. Requires node name and container ID.
    MIT
  • Retrieve the current runtime status of an LXC container, including running/stopped state, CPU, and memory usage, by specifying the node and container ID.
    MIT
  • Permanently delete an LXC container snapshot by specifying node, container ID, and snapshot name. Irreversible action requires elevated risk level.
    MIT
  • Capture real email screenshots across 15 email clients with light and dark mode variants. Renders emails in real browsers and hosts screenshots on CDN for compatibility testing.
    MIT
  • Create LXC containers in Proxmox VE from templates with configurable resources like CPU cores, memory, storage, and network settings.
    MIT
  • List all LXC containers across the Proxmox cluster with optional node-based filtering to view containers on a specific node.
    MIT