Gemini CLI | Stoaken Integrations

What it does

Gemini CLI reads your Brands and tokens, exports them as code and proposes token changes for a person to approve. The tools are listed at /docs/mcp.

Before you start

A Stoaken account with at least Viewer on a Brand. On the Free plan agents are read only.
Gemini CLI. For unpaid-tier and Google One users, Google replaced it with Antigravity CLI on 18 June 2026.
Optional: an API key from Settings > API keys.

Setup

npx stoaken init --client gemini-cli
gemini trust

init writes .gemini/settings.json, keeping your other settings. Untrusted folders ignore that file and connect no MCP servers, hence gemini trust. Then, inside Gemini CLI, run /mcp auth stoaken to sign in in the browser (Gemini CLI discovers Stoaken's sign-in and registers itself).

Or add it by hand: gemini mcp add --transport http stoaken https://www.stoaken.com/mcp.

Configuration

{
  "mcpServers": {
    "stoaken": { "httpUrl": "https://www.stoaken.com/mcp" }
  }
}

httpUrl is streamable HTTP; url would mean the older SSE transport. With an API key instead of OAuth:

{
  "mcpServers": {
    "stoaken": {
      "httpUrl": "https://www.stoaken.com/mcp",
      "headers": { "Authorization": "Bearer ${STOAKEN_API_KEY}" }
    }
  }
}

Gemini CLI expands ${VAR} in settings strings, so the key stays in your shell, not the file.

Try it

"Use the stoaken tools to list my Brands."
"Export the Default theme as Tailwind 4 and update src/theme.css."

Troubleshooting

Server missing from /mcp list: the folder isn't trusted, so .gemini/settings.json was ignored.
OAuth doesn't start: sign-in needs a local browser and a localhost redirect; over SSH or in a container use the API key.
401 with an API key: STOAKEN_API_KEY isn't set where Gemini CLI runs.
Don't set trust: true on stoaken; keep confirmations for propose_* tools.

Limits

No tool approves or publishes a release.
Writes count towards a per-key limit; Free plan is read only.
Antigravity CLI is a separate product; this guide doesn't cover it.