When using a configuration file like
{
"servers": {
"internal-service": {
"url": "${cmd: jq -r '.internal-service.url' secrets.json}"
}
}
}the placeholder is not resolved therefore starting the server fails with an invalid server URL error.
The documentation hints that it's possible given the code example right after the Universal Placeholder Syntax secion:
{
"mcpServers": {
"remote-server": {
"url": "https://${PRIVATE_DOMAIN}/mcp",
"headers": {
"Authorization": "Bearer ${cmd: op read op://vault/api/token}",
"X-Custom-Header": "${CUSTOM_VALUE}"
}
}
}
}Using a variable like in the code snippet works but the extended functionality of placeholders isn't available and it is not possible to create an ENV in the configuration and reference it in the URL.
When using a configuration file like
{ "servers": { "internal-service": { "url": "${cmd: jq -r '.internal-service.url' secrets.json}" } } }the placeholder is not resolved therefore starting the server fails with an invalid server URL error.
The documentation hints that it's possible given the code example right after the Universal Placeholder Syntax secion:
{ "mcpServers": { "remote-server": { "url": "https://${PRIVATE_DOMAIN}/mcp", "headers": { "Authorization": "Bearer ${cmd: op read op://vault/api/token}", "X-Custom-Header": "${CUSTOM_VALUE}" } } } }Using a variable like in the code snippet works but the extended functionality of placeholders isn't available and it is not possible to create an ENV in the configuration and reference it in the URL.