env_var_expansion
Whether MCP server configuration supports environment variable expansion. Reduces the need for hardcoded secrets in config files.
Type: bool Content type: mcp
Provider Support
Section titled “Provider Support”| Provider | Supported | Mechanism |
|---|---|---|
| claude-code | ✓ | mcp_env_var_expansion: ${VAR} and ${VAR:-default} syntax in command, args, env, url, and headers fields of .mcp.json |
| crush | ✓ | env_variable_expansion: Crush MCP configuration supports environment variable references in server env blocks |
| cursor | ✓ | Server env blocks reference environment variables so secrets can be read from the shell environment rather than hardcoded. |
| gemini-cli | ✓ | env_variable_expansion: Gemini CLI MCP configuration supports environment variable expansion for secrets and paths |
| opencode | ✓ | env_variable_expansion: environment variables configured in server env blocks |
| roo-code | ✓ | env_variable_expansion: server env blocks accept environment variables so secrets can be referenced from the shell environment |
| windsurf | ✓ | config_interpolation: Windsurf MCP configuration supports ${VAR} interpolation for environment variables |
| amp | ✗ | Amp MCP configuration does not document environment variable expansion |
| cline | ✗ | Cline MCP configuration does not document environment variable expansion syntax |
| codex | ✗ | Codex MCP configuration does not document environment variable expansion |
| copilot-cli | ✗ | Copilot CLI MCP configuration does not document environment variable expansion |
| factory-droid | ✗ | Factory Droid MCP configuration does not document environment variable expansion |
| kiro | ✗ | Kiro MCP configuration does not document environment variable expansion |
| zed | ✗ | no automatic environment variable expansion documented in Zed MCP env blocks |