This configuration pattern is for a VS Code setup that supports remote HTTP MCP servers and prompted inputs. It is a starting point for the connection agreed during onboarding, not a claim that every extension or organisation policy supports MCP.
Prepare the configuration#
Use VS Code's current MCP configuration command or the appropriate MCP configuration file. A workspace file may be shared with your project, so never put the raw credential in it.
The example below uses a deliberately non-working placeholder endpoint. Replace the address with the one assigned by DigLab. Leave the password prompt in place.
{
"servers": {
"mcp-diglab": {
"type": "http",
"url": "https://mcp.diglab.ai/mcp/YOUR_ASSIGNED_CONNECTION",
"headers": {
"X-API-Key": "${input:diglab-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "diglab-key",
"description": "Your assigned MCP DigLab key",
"password": true
}
]
}Connect and test#
Save the configuration and use VS Code's MCP controls to start or reconnect the server. Enter the assigned credential only in the prompted field. Review the tools presented by the client, then run the read-only test from your handoff.
If the connection is trusted or approved by your organisation, follow its normal policy. Do not disable workspace safeguards to make the example work.
Keep the configuration safe#
The placeholder file is safe to discuss; the actual key is not. When reporting a problem, remove the credential and private account details from any screenshots or logs. Replacing a key inside a screenshot is not enough if the same value remains elsewhere in an attached file.
For current client-specific options, consult the official VS Code MCP guide. Return to quick start once the connection is running.