Problem
After nao deploy, the project is copied to nao Cloud and environment variable placeholders declared in nao_config.yml are surfaced in the UI, where they can be filled in.
But placeholders that only appear in the MCP config file are not picked up. A user with "DBT_TOKEN": "${DBT_TOKEN}" in their MCP config has no way to set DBT_TOKEN from the UI, so the variable is never substituted and the MCP server fails to start on the deployed environment.
There is no workaround from the UI: the variable simply is not listed.
Expected behavior
nao deploy should collect env var placeholders from the MCP config file as well as from nao_config.yml, expose them all in the cloud UI, and substitute the values at runtime the same way nao_config.yml placeholders are substituted.
Customer ID
698c318e-7b1d-4cb4-821d-a38d9f09ecee
Problem
After
nao deploy, the project is copied to nao Cloud and environment variable placeholders declared innao_config.ymlare surfaced in the UI, where they can be filled in.But placeholders that only appear in the MCP config file are not picked up. A user with
"DBT_TOKEN": "${DBT_TOKEN}"in their MCP config has no way to setDBT_TOKENfrom the UI, so the variable is never substituted and the MCP server fails to start on the deployed environment.There is no workaround from the UI: the variable simply is not listed.
Expected behavior
nao deployshould collect env var placeholders from the MCP config file as well as fromnao_config.yml, expose them all in the cloud UI, and substitute the values at runtime the same waynao_config.ymlplaceholders are substituted.Customer ID
698c318e-7b1d-4cb4-821d-a38d9f09ecee