The MCP container deployment requires manual intervention after every restart:
Docker network not persistent — docker network connect ayon-private_default mcp-ayon is lost on every container recreate. DNS resolution for ayon-private-server-1 does not work cross-network, forcing hardcoded IP (192.168.64.4) in .env.
API key rot — Stored in .env, can be silently invalidated or corrupted (observed: key became *** in file after Hermes secret redaction). Requires manual key regeneration via AYON WebUI.
Wrong AYON instance detection — MCP was configured to use original instance (port 5000, ayon-docker_default network) instead of the private clone (port 5001, ayon-private_default network). This was silently failing.
Impact
Every MCP restart costs 5-10 manual fix steps before publishing works.
Proposed Fix
Declare ayon-private_default as external network in compose.yml with health checks
Use Docker secrets or a config volume instead of .env for the API key
Add a startup check that validates the API key against the configured AYON instance and fails fast with a clear error
## Problem
The MCP container deployment requires manual intervention after every restart:
1. **Docker network not persistent** — `docker network connect ayon-private_default mcp-ayon` is lost on every container recreate. DNS resolution for `ayon-private-server-1` does not work cross-network, forcing hardcoded IP (192.168.64.4) in `.env`.
2. **API key rot** — Stored in `.env`, can be silently invalidated or corrupted (observed: key became `***` in file after Hermes secret redaction). Requires manual key regeneration via AYON WebUI.
3. **Wrong AYON instance detection** — MCP was configured to use original instance (port 5000, `ayon-docker_default` network) instead of the private clone (port 5001, `ayon-private_default` network). This was silently failing.
## Impact
Every MCP restart costs 5-10 manual fix steps before publishing works.
## Proposed Fix
- Declare `ayon-private_default` as external network in compose.yml with health checks
- Use Docker secrets or a config volume instead of `.env` for the API key
- Add a startup check that validates the API key against the configured AYON instance and fails fast with a clear error
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Problem
The MCP container deployment requires manual intervention after every restart:
docker network connect ayon-private_default mcp-ayonis lost on every container recreate. DNS resolution forayon-private-server-1does not work cross-network, forcing hardcoded IP (192.168.64.4) in.env..env, can be silently invalidated or corrupted (observed: key became***in file after Hermes secret redaction). Requires manual key regeneration via AYON WebUI.ayon-docker_defaultnetwork) instead of the private clone (port 5001,ayon-private_defaultnetwork). This was silently failing.Impact
Every MCP restart costs 5-10 manual fix steps before publishing works.
Proposed Fix
ayon-private_defaultas external network in compose.yml with health checks.envfor the API key