Warn if config schema can not be validated at runtime

[slimslenderslacks]

If the gateway attempts to start an MCP server with missing config, we may see errors like:

Listing MCP tools...
  - Running mcp/filesystem with [run --rm -i --init --security-opt no-new-privileges --cpus 1 --memory 2Gb --pull never -l docker-mcp=true -l docker-mcp-tool-type=mcp -l docker-mcp-name=filesystem -l docker-mcp-transport=stdio --network none]
  > Can't start filesystem: failed to connect: calling "initialize": EOF

In the example above, the underlying problem is that the mcp/filesystem container was started without a paths input. If we validate the gateway configuration against the MCP config schema, we would have at least been able to warn the user about a missing required config property.

[riturajFi]

Hi @slimslenderslacks , i would love to take this up!