Gemini CLI Sugra API call_endpoint

How to: Gemini CLI Sugra API call_endpoint

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

Add Sugra API to Gemini CLI

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

{
  "mcpServers": {
    "api-mcp": {
      "httpUrl": "https://app.sugra.ai/mcp"
    }
  }
}

02
Save the file and restart Gemini CLI.
03
Ask for something call_endpoint does. Gemini CLI lists the server's tools on connect and calls call_endpoint itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that Sugra API'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

Sugra API will not start until these are set, so call_endpoint never becomes available.

SUGRA_API_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.

Sugra API MCP server