Gemini CLI & Gemini Code Assist

Connect Forvibe to Gemini CLI or supported Gemini Code Assist agent mode.

Updated 2026-09-23
3 min read

Gemini CLI reads MCP servers from ~/.gemini/settings.json or a project's .gemini/settings.json. The same format is used by supported Gemini Code Assist Standard and Enterprise agent-mode installations in VS Code and JetBrains.

This page does not describe the retired Gemini Code Assist Individual service. Use Gemini CLI, or a current Code Assist Standard or Enterprise installation that exposes MCP in Agent mode.

Setup

1

Create a Forvibe API key

Create a dedicated key at Settings → API Keys, then expose it to the Gemini process:

bash
export FORVIBE_API_KEY="fvk_live_..."
2

Add the server to settings.json

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

Gemini uses httpUrl for Streamable HTTP and expands $VAR or ${VAR} values from its environment. The 120-second timeout matches Forvibe's maximum request duration for longer AI operations.

3

Reload and verify

bash
gemini mcp list

Restart the IDE if you use Code Assist. In Gemini CLI or Agent mode, ask: Use Forvibe to list my projects.

Gemini CLI supports OAuth discovery in general, but Forvibe's Gemini OAuth interoperability is not listed as a verified setup path here. Use the API-key configuration above until the end-to-end browser flow is explicitly validated.