Connect VS Code
VS Code (1.99+) has built-in MCP support, consumed by Copilot agent mode. Servers can be configured per workspace or per user.
Prerequisites
- VS Code 1.99 or later with GitHub Copilot enabled
- A Wicket member key — see the Quickstart if you don’t have one yet
Configuration
Create .vscode/mcp.json in your repo. Use an input so the key is prompted once and stored in VS Code’s secret storage — never committed:
{ "inputs": [ { "type": "promptString", "id": "wicket-key", "description": "Wicket member key", "password": true } ], "servers": { "wicket": { "type": "http", "url": "https://mcp.wicket.sh/mcp", "headers": { "Authorization": "Bearer ${input:wicket-key}" } } }}VS Code prompts for the key the first time the server starts.
Run MCP: Add Server from the command palette, choose HTTP, and enter https://mcp.wicket.sh/mcp. Then open the generated user mcp.json (MCP: Open User Configuration) and add the Authorization header with your member key, or wire an input as in the workspace tab.
Verify
- Run MCP: List Servers from the command palette —
wicketshould show as running. - Open Copilot Chat in Agent mode, click the tools icon —
github__*(and other connected services’) tools are listed. - Ask: List my GitHub repositories. The call appears in the Wicket Audit tab.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| Server missing from MCP: List Servers | mcp.json malformed, or workspace not trusted |
| Key prompt never appeared | Remove the server’s cached input: MCP: Reset Cached Tools, restart the server |
401 Unauthorized | Wrong or rotated member key — regenerate in Wicket |
403 Forbidden | Agent disabled or member not approved |
| Tool call blocked | Policy deny — check the Audit tab for the matched rule |
Using Cline or Continue instead of native Copilot? See Connect Cline / Continue.