Skip to main content
Glama
548,434 tools. Updated 2026-09-11 12:08

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

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
    7
    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.

  • 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
  • Remove an MCP server from your AI client's configuration by specifying the server name. Supports removing from multiple clients at once.
    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
  • Return the current Dali server version and changelog to verify MCP server connectivity and debug version mismatches between the pip package and hosted API.
    MIT
  • Get a plain-text summary of AnythingMCP, a self-hosted gateway that turns REST, SQL, and other APIs into MCP tools. Includes links to docs, GitHub, and cloud—start here before installing or connecting clients.
    AGPL 3.0
  • Learn the recommended workflow for AI clients using ChimeraX MCP, including how to start, inspect, and control ChimeraX without direct shell launches.
    MIT
  • Retrieve all VMs and LXC containers across Proxmox nodes with status, node placement, and resource allocation details including CPU, memory, and disk.
    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
  • Migrate a VM or container to another Proxmox node, with live migration for running QEMU VMs and restart migration for LXC containers.
    MIT