Describe the feature or problem you'd like to solve
Support of environment variable in MCP-Config
Proposed solution
Simply supports that. It is major I think because it forces us to add our secrets into the MCP config (which I am not a fan of ;) )
best regards
Example prompts or workflows
in $HOME/.copilot/mcp-config.json
"${COPI_COAIAN_MCP_NAME}": {
"type": "local",
"command": "npx",
"tools": [ "*" ],
"args": ["-y", "${CNCV}", "--memory-path", "${COPI_COAIAN_MCP_MF}"]
}
{
"mcpServers": {
"github_mcp": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-github"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PERSONAL_ACCESS_TOKEN}"
}
}
}
}
Additional context
- Gemini-cli, claude-code supports that...
Describe the feature or problem you'd like to solve
Support of environment variable in MCP-Config
Proposed solution
Simply supports that. It is major I think because it forces us to add our secrets into the MCP config (which I am not a fan of ;) )
best regards
Example prompts or workflows
in $HOME/.copilot/mcp-config.json
Additional context