Gemini Code Assist & Gemini CLI

Google's Gemini Code Assist (VS Code / JetBrains plugin) and the Gemini CLI share a single MCP config: ~/.gemini/settings.json (global) or .gemini/settings.json in any project root. Streamable HTTP is fully supported, including OAuth 2.0 if you'd rather skip pasting a key.

Setup

Mint an API key

Open Settings → API Keys, create a key named e.g. "Gemini", copy the fvk_live_… token.

Edit settings.json

Create the file if it doesn't exist. Gemini uses httpUrl (not url) so it can route HTTP and stdio servers from the same config block:

json

{
  "mcpServers": {
    "forvibe": {
      "httpUrl": "https://www.forvibe.app/mcp",
      "headers": {
        "Authorization": "Bearer ${FORVIBE_API_KEY}"
      },
      "timeout": 60000
    }
  }
}

Then export the key in your shell startup file:

bash

export FORVIBE_API_KEY="fvk_live_..."

Gemini interpolates both ${VAR_NAME} and $VAR_NAME forms from your process environment. The 60-second timeout is plenty for every Forvibe tool except simulate_metadata_only, which can take up to 90s — bump that one to 120000 if you run it often.

Reload the agent

Gemini Code Assist: restart VS Code / JetBrains so the plugin re-reads settings.json.
Gemini CLI: run gemini mcp list to confirm Forvibe shows up. The CLI re-reads the config on every invocation.

Verify

bash

gemini mcp list                   # should list "forvibe"
gemini "List my Forvibe projects" # should call list_projects

Prefer OAuth? Omit the headers block entirely — Gemini will trigger Forvibe's browser consent flow on the first connect attempt and store the resulting tokens automatically.