Gemini CLI Flux Cloud flux_deploy_app

How to: Gemini CLI Flux Cloud flux_deploy_app

client:Gemini CLI transport:streamable-http tool:flux_deploy_app

Add Flux Cloud to Gemini CLI

01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "flux-cloud-mcp": {
      "httpUrl": "https://mcp.runonflux.com/mcp"
    }
  }
}

02
Save the file and restart Gemini CLI.
03
Ask for something flux_deploy_app does. Gemini CLI lists the server's tools on connect and calls flux_deploy_app itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that Flux Cloud's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Set these first

Flux Cloud will not start until these are set, so flux_deploy_app never becomes available.

FLUX_ID_PRIVATE_KEY
FLUX_PAYMENT_PRIVATE_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

Flux Cloud MCP server