VS Code

Copilot’s agent mode, with the key prompted rather than stored.

Setup

1. Create .vscode/mcp.json with the block below.
2. Open Chat and switch to Agent mode.
3. VS Code prompts for the key the first time and stores it in the OS keychain.
4. Use the tools picker to confirm the six tools are available.

{
  "inputs": [
    {
      "id": "unzoi-key",
      "type": "promptString",
      "description": "Unzoi API key",
      "password": true
    }
  ],
  "servers": {
    "unzoi": {
      "type": "http",
      "url": "https://api.unzoi.com/mcp",
      "headers": { "x-api-key": "${input:unzoi-key}" }
    }
  }
}

What differs here

• The `inputs` block is the reason to prefer VS Code for a shared repository: the file names the key without containing it, and each developer supplies their own on first use. Nothing secret is committed.
• Note the key is `servers`, not `mcpServers` — VS Code differs from most other clients here, and a file using the wrong key is silently ignored.
• Tools are only available in Agent mode, not in Ask mode.

Next

• Get a key at console.unzoi.com, if you have not.
• The tool reference — what the model is reading when it chooses between the six tools.
• Stories for context windows — the one habit that most changes how well an agent works against this API.
• Limits — an agent that loops can spend a monthly quota faster than you expect.
• VS Code's own MCP documentation — authoritative for anything about the client itself, including config paths, which move.

Endpoint, for copying: https://api.unzoi.com/mcp