Gemini CLI AI Wave list_model_changes

How to: Gemini CLI AI Wave list_model_changes

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

Add AI Wave to Gemini CLI

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

{
  "mcpServers": {
    "ai-wave": {
      "httpUrl": "https://aiwave.elopstudio.com/api/mcp"
    }
  }
}

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

AI Wave will not start until these are set, so list_model_changes never becomes available.

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

AI Wave MCP server