Split secrets from MCP configs #349
Description
Describe the feature or problem you'd like to solve
Configs should receive secrets from a different file
Proposed solution
A file at ~/.copilot/.env could be used to store secrets separately from the configs.
Example prompts or workflows
This would allow open-sourcing one's dotfiles.
Example with Gemini CLI:
Example with VSCode:
Additional context
This is already supported by other programs. Here's some examples.
VSCode:
{
"inputs": [
{
"description": "Tavily API Key",
"id": "tavily_api_key",
"password": true,
"type": "promptString"
}
],
"servers": {
"tavily": {
"args": ["tavily-mcp@latest"],
"command": "bunx",
"env": { "TAVILY_API_KEY": "${input:tavily_api_key}" },
"type": "stdio"
}
}
}And in Gemini CLI:
{
"mcpServers": {
"tavily": {
"args": ["tavily-mcp@latest"],
"command": "bunx",
"env": { "TAVILY_API_KEY": "$TAVILY_API_KEY" },
"trust": true
}
}
}