Skip to content

Gemini CLI LLMIntel Model Lifecycle recent_lifecycle_changes

How to: Gemini CLI LLMIntel Model Lifecycle recent_lifecycle_changes

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

Add LLMIntel Model Lifecycle to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "model-lifecycle": {
      "httpUrl": "https://llmintel.ai/v1/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    Ask for something recent_lifecycle_changes does. Gemini CLI lists the server's tools on connect and calls recent_lifecycle_changes itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that LLMIntel Model Lifecycle'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

LLMIntel Model Lifecycle will not start until these are set, so recent_lifecycle_changes never becomes available.

  • LLMINTEL_API_KEY
  • LLMINTEL_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.