Skip to content

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.

Verify

  1. Run MCP: List Servers from the command palette — wicket should show as running.
  2. Open Copilot Chat in Agent mode, click the tools icon — github__* (and other connected services’) tools are listed.
  3. Ask: List my GitHub repositories. The call appears in the Wicket Audit tab.

Troubleshooting

SymptomLikely cause
Server missing from MCP: List Serversmcp.json malformed, or workspace not trusted
Key prompt never appearedRemove the server’s cached input: MCP: Reset Cached Tools, restart the server
401 UnauthorizedWrong or rotated member key — regenerate in Wicket
403 ForbiddenAgent disabled or member not approved
Tool call blockedPolicy deny — check the Audit tab for the matched rule

Using Cline or Continue instead of native Copilot? See Connect Cline / Continue.