VS Code

Connect Forvibe to native MCP support in VS Code with GitHub Copilot Agent mode.

Updated 2026-09-23
4 min read

This guide covers VS Code's native MCP integration for GitHub Copilot Chat. MCP tools are used from Agent mode, not Ask or Edit mode.

Desktop VS Code setup

1

Create a protected API-key input

Create a key at Settings → API Keys. Run MCP: Add Server from the Command Palette and choose HTTP, or create .vscode/mcp.json with the current servers schema:

json
{
  "inputs": [
    {
      "id": "forvibeApiKey",
      "type": "promptString",
      "description": "Forvibe API key (fvk_live_...)",
      "password": true
    }
  ],
  "servers": {
    "forvibe": {
      "type": "http",
      "url": "https://forvibe.app/mcp",
      "headers": {
        "Authorization": "Bearer ${input:forvibeApiKey}"
      }
    }
  }
}

VS Code prompts for the value and keeps it out of the shared JSON file. Do not replace the input variable with a literal key in a committed workspace config.

2

Start the server

Use the Start action above the server entry or run MCP: List Servers and select forvibe. Approve the server trust prompt, then enter the API key when requested.

3

Enable the tools

Open Copilot Chat, switch to Agent, open the tools picker, and enable forvibe. Ask: Use Forvibe to list my projects.

User, workspace, and Agent Host configuration

  • Use MCP: Open User Configuration for a machine-local server available in every workspace.
  • Use .vscode/mcp.json when the team should share the server definition; keep the credential as a protected input.
  • Agent Host does not directly read .vscode/mcp.json and does not forward interactive ${input:…} values. For a portable non-interactive setup, use a workspace .mcp.json or user ~/.copilot/mcp-config.json and configure its credential through the host's supported secret mechanism.

VS Code supports OAuth for remote MCP servers when its OAuth configuration is available. Forvibe's automatic VS Code OAuth registration is not presented here as a verified path; the protected API-key flow above matches the current native configuration schema and works without a manually registered OAuth client ID.