Aller au contenu
Se connecter

Accès par défaut

Adresse
http://ADRESSE-IP:8080Remplacez ADRESSE-IP par l'adresse donnée à la fin de l'installation.
Compte
admin
Console et SSH
Console du conteneur dans l'interface Proxmox : compte root, connexion automatique sans mot de passe. Le SSH de root n'est ouvert que si vous l'avez demandé à l'installation.
Configuration
/opt/agentgateway
  • Public listener is 0.0.0.0:8080 (var_public_port, default 8080). UI: http://<container-ip>:8080/ui with HTTP basic auth (default user admin, random password). MCP Streamable HTTP: http://<container-ip>:8080/mcp/http (also /mcp and /sse). Copy /opt/agentgateway/mcp_client.json into your MCP client's config (Bearer API key). MCP also accepts the same basic-auth credentials. Tools are always prefixed with the target name (prefixMode: always). One dead backend does not fail the whole session (failureMode: failOpen).
  • Unattended: bash -c "$(curl -fsSL https://raw.githubusercontent.com/oraad/proxmox-scripts/main/ct/agentgateway.sh)". Optional backends: var_mcp_targets='home=http://192.168.1.21:8086/mcp-<secret>' (exact URL from pct exec <ha-mcp-CTID> -- cat /opt/ha-mcp/mcp_endpoint.txt). Optional: var_public_port=8080 (alias var_mcp_port), var_ui_user=admin, var_ui_password=..., var_api_key=.... Loopback admin: var_admin_port=15000 var_admin_bind=127.0.0.1.
  • Config: /opt/agentgateway/config.yaml (mode 600, user agentgateway). Basic-auth hashes live in /opt/agentgateway/htpasswd. Saving in the UI overwrites config.yaml and strips comments. config.* binds and session.key are only applied at process start — restart after changing them. Most other YAML edits hot-reload.
  • Retrieve the MCP URL with pct exec <CTID> -- cat /opt/agentgateway/mcp_endpoint.txt. UI URL: pct exec <CTID> -- cat /opt/agentgateway/ui_url.txt. MCP client snippet: pct exec <CTID> -- cat /opt/agentgateway/mcp_client.json. Secrets (API key, UI password): pct exec <CTID> -- grep -E 'AGENTGATEWAY_API_KEY|UI_USER|UI_PASSWORD' /opt/agentgateway/.env.

Valeurs publiques de l'éditeur : changez-les dès la première connexion.

Deploys the official agentgateway binary as an MCP federation proxy. One public HTTP listener on port 8080 serves the UI (HTTP basic auth) and a Streamable HTTP MCP endpoint (Bearer API key or the same basic-auth credentials) that multiplexes tools from backends such as ha-mcp LXCs.

Site ↗ Documentation ↗ Voir le code du script ↗

Installer

Cœurs
1
Mémoire
1 Go
Disque
4 Go
Système
Debian 13
bash -c "$(curl -fsSL https://raw.githubusercontent.com/oraad/proxmox-scripts/main/ct/agentgateway.sh)"

Configuration : /opt/agentgateway

Dans le shell du nœud Proxmox. Exécutez cette commande dans le shell du nœud Proxmox, pas dans une VM. Lisez le script d'abord.

Tutoriel pas à pas

De l'interface de Proxmox jusqu'à la première connexion, pour Agent Gateway.

  1. Ouvrez l'interface de Proxmox dans votre navigateur et connectez-vous.

  2. Dans l'arbre de gauche, cliquez sur votre nœud, puis sur « Shell ».

  3. Vérifiez que le nœud a la place pour ce conteneur : 1 cœur, 1 Go de mémoire, 4 Go de disque.

  4. Copiez cette commande, collez-la dans le shell et appuyez sur Entrée.

    bash -c "$(curl -fsSL https://raw.githubusercontent.com/oraad/proxmox-scripts/main/ct/agentgateway.sh)"
  5. Attendez la fin de l'installation : le script affiche l'adresse du conteneur.

  6. Ouvrez http://ADRESSE-IP:8080 dans votre navigateur, en remplaçant ADRESSE-IP par l'adresse affichée.

  7. Connectez-vous avec le compte admin, puis changez tout de suite le mot de passe.

  8. Pour mettre à jour plus tard : tapez update dans la console du conteneur.

  9. Le fichier de configuration se trouve ici : /opt/agentgateway

À savoir

  • UI and MCP share one 1.4 gateways listener. Two strict auth policies would both have to succeed (AND), so MCP uses optional apiKey + optional basicAuth plus a CEL allow rule so Bearer token OR basic auth works. UI uses basicAuth mode strict only. Basic auth is not TLS; keep this on a LAN or behind a TLS reverse proxy.
  • Prometheus metrics (15020) and readiness (15021) bind to 127.0.0.1. The process also keeps an unauthenticated loopback admin socket on 127.0.0.1:15000 as break-glass (not advertised; do not publish 15000/15020/15021). Optional: var_admin_port / var_admin_bind — leave bind at 127.0.0.1.
  • Install does not prompt for backends. After install, add Streamable HTTP servers in the UI (MCP → Servers) or in /opt/agentgateway/config.yaml under mcp.targets. Example: name home, URL from pct exec <CTID> -- cat /opt/ha-mcp/mcp_endpoint.txt. Target names: letters, digits, hyphens only (no underscores). mcp.targets must be present even if empty (targets: []).
  • Keep one ha-mcp LXC per Home Assistant. This gateway federates their HTTP endpoints and never sees HA tokens. Do not also register the same ha-mcp URLs directly in the MCP client.
  • Update an existing container: run update inside the LXC, or pct exec <CTID> -- update from the Proxmox host. Updates replace the binary and leave config.yaml / .env in place. Dry-run via PVE LXC Apps Updater works (check_for_gh_release).
  • Service status — Debian: systemctl status agentgateway and journalctl -u agentgateway -n 50. Alpine: rc-service agentgateway status and tail -50 /var/log/agentgateway.log. Official docs: https://agentgateway.dev/docs/standalone/latest/mcp/connect/virtual/
  • Alpine template: run pveam update, then pveam available --section system | grep alpine-3.24. Download if missing: pveam download local alpine-3.24-default_20260116_amd64.tar.xz (use the exact name from pveam available on your arch). Fallback: var_version=3.22 if 3.24 is not listed on an older Proxmox host. The upstream binary is musl (amd64/arm64).
  • Debian 13 and Alpine installs enable nesting and keyctl by default (Debian: systemd compatibility; Alpine: Docker and tunnel agents).
Dans la même catégorie

ESPConnect

Conteneur LXC

ESPConnect is a zero-installation web application that lets you explore, back up, and manage ESP32 devices from a browser.

Mise à jour Port 443

ESPHome

Conteneur LXC

ESPHome is a platform for controlling ESP8266/ESP32-based devices using configuration files and integrating them with Home Automation systems. It provides a simple and f…

Mise à jour Port 6052

FHEM

Conteneur LXC

FHEM stands for "Freundliche Hausautomation und Energie-Messung," which translates to "Friendly Home Automation and Energy Measurement" in English. The software can inte…

Mise à jour Port 8083

HA MCP

Conteneur LXC oraad — proxmox-scripts

Deploys the official Home Assistant MCP Server (ha-mcp) in HTTP mode via uvx. Provides a LAN MCP endpoint for HTTP-capable MCP clients to control Home Assistant through …

Mise à jour Port 8086

Home Assistant Container

Conteneur LXC

A standalone container-based installation of Home Assistant Core means that the software is installed inside a Docker container, separate from the host operating system.…

Mise à jour Port 8123

Home Assistant OS

Machine virtuelle

Home Assistant OS is the appliance image of Home Assistant, managing its own supervisor and add-ons. This installs the official image as a VM.

Port 80