Gemini CLI Proof Holdings export_authorizations

How to: Gemini CLI Proof Holdings export_authorizations

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

Add Proof Holdings to Gemini CLI

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

{
  "mcpServers": {
    "mcp-server": {
      "httpUrl": "https://api.proof.holdings/mcp"
    }
  }
}

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

Proof Holdings will not start until these are set, so export_authorizations never becomes available.

PROOF_API_KEY
PROOF_BASE_URL

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.

Proof Holdings MCP server