VS Code Setup Guide

0. Prerequisites

• Access to GitHub Copilot in VS Code.
• MCP tools show up in Copilot Chat (typically in Agent mode).

1. Add Server

VS Code supports MCP servers via the Command Palette or by editing mcp.json directly. MCP server configuration uses servers (not mcpServers).

VS Code supports both workspace-level and global MCP server config. For workspace config, use .vscode/mcp.json. For global config, use Command Palette → MCP: Open User Configuration.

Option A: Command Palette

1. Open Command Palette: Cmd/Ctrl+Shift+P
2. Run MCP: Add Server
3. Choose HTTP (Streamable). VS Code will fall back to SSE if HTTP stream is not supported.
4. Name: unified-proxy
5. URL: https://zephex.dev/mcp/mcp
6. Add header: Authorization: Bearer YOUR_API_KEY

When prompted, choose Workspace to write .vscode/mcp.json, or Global to add the server to your user profile.

Option B: Edit Config File

Recommended: Create .vscode/mcp.json in your project root. This uses an inputs prompt so you don't have to store your API key in plain text:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "mcp-proxy-api-key",
      "description": "Zephex API key",
      "password": true
    }
  ],
  "servers": {
    "unified-proxy": {
      "type": "http",
      "url": "https://zephex.dev/mcp/mcp",
      "headers": {
        "Authorization": "Bearer ${input:mcp-proxy-api-key}",
        "X-API-Source": "vscode"
      }
    }
  }
}

2. Reload VS Code

Run Developer: Reload Window from the command palette (Cmd/Ctrl+Shift+P).

3. Verify

Open Copilot Chat, switch to Agent mode, click the tools icon, and confirm tools from unified-proxy are listed.

4. Settings Sync (Optional)

With Settings Sync enabled, VS Code can synchronize MCP server configurations across devices. Use Settings Sync: Configure and ensure MCP Servers is included in the sync list.