VS Code should use the native stdio MCP config with a secure key prompt. Do not use the older hosted HTTP config for this setup.
OVERVIEW
VS Code can prompt for the API key instead of hardcoding it in the config file. For Zephex, the reliable setup is a stdio MCP server entry that runs `npx -y zephex` and injects the prompted key through the env block.
CONFIG FILE LOCATION
Create this file: .vscode/mcp.json in your workspace root directory.
Paste the JSON exactly as shown. VS Code prompts for the API key from the input block and passes it into `ZEPHEX_API_KEY` when it starts the local MCP process.
The `${input:zephex-api-key}` value is correct. VS Code resolves it at runtime when the server first starts.
{ "inputs": [ { "type": "promptString", "id": "zephex-api-key", "description": "Zephex API Key", "password": true } ], "servers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "${input:zephex-api-key}" } } }}Use the MCP panel or chat tool picker to confirm VS Code loaded the MCP server.
The workspace usually was not reloaded after the file changed. Run "Developer: Reload Window" again, then open a new chat session.
Make sure the server block uses `command`, `args`, and `env` exactly as shown above instead of the older HTTP fields.
Check that .vscode/mcp.json is valid JSON with no comments or trailing commas. Also verify the top-level key is `servers`, not `mcpServers`.
Make sure the file is in the currently opened workspace root under .vscode/mcp.json. If you edited another repo or a parent folder, VS Code will not load it for this workspace.
If the editor still does not connect, return to Quickstart or check Connection Issues.