Gemini CLI Sugra API Resource/attribution

How to: Gemini CLI Sugra API attribution

client:Gemini CLI transport:streamable-http resource:attribution

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
attribution is surfaced wherever your client lets you attach context. It is context to attach, not an action to run.
04
If it does not appear, check that Sugra API is connected and that you are looking at its resources rather than its tools.

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 it never reaches Gemini CLI.

SUGRA_API_KEY

Same resource, other clients

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.

Sugra API MCP server