Skip to main content
The Gemini CLI supports remote MCP servers over HTTP, including the OAuth sign-in flow, so Superflow only needs a config entry.

Setup

Add Superflow to ~/.gemini/settings.json:
~/.gemini/settings.json
Restart the CLI. The first time it calls a Superflow tool it opens your browser to sign in and approve the scopes. Run /mcp inside the CLI to list connected servers and their tools, then try ā€œlist my Superflow projectsā€. The tools show up named mcp_superflow_superflow_....
Gemini CLI starts MCP servers only in a folder you trust. It asks the first time you open a folder. For a headless gemini -p run, pass --skip-trust or set GEMINI_CLI_TRUST_WORKSPACE=true.

Use an API key instead

Run the local package with an API key:
Do not put -- before npx here. gemini mcp list should then show superflow as Connected. See use the local package for the browser sign-in and read-only mode.
Gemini’s CLI has changed its config format across releases, and Google is folding the Gemini CLI into the Antigravity CLI. The mcpServers block carries over, but if the server doesn’t show up in /mcp, check the key name for remote HTTP servers in your version’s documentation. Some releases use url rather than httpUrl.

Managing the connection

Delete the superflow entry from settings.json to disconnect. To revoke the grant, also revoke it in Superflow under Settings > Integrations > API keys, in Connected AI apps.