VS Code should use the HTTP MCP config with a secure key prompt. The hosted endpoint connects directly to Zephex without local processes.
OVERVIEW
VS Code can prompt for the API key instead of hardcoding it in the config file. For Zephex, use the HTTP server entry that connects directly to https://zephex.dev/mcp with the API key passed as a Bearer token in headers.
CONFIG FILE LOCATION
Create this file: .vscode/mcp.json in your workspace root directory.
Run the command below.
npx zephex setup --vscodePaste the JSON exactly as shown. VS Code prompts for the API key from the input block and passes it as a Bearer token in the Authorization header when connecting to the hosted endpoint.
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": { "type": "http", "url": "https://zephex.dev/mcp", "headers": { "Authorization": "Bearer ${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 `type`, `url`, and `headers` exactly as shown above.
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.