Gemini CLI Chain Daddy create_alert_rule

How to: Gemini CLI Chain Daddy create_alert_rule

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

Add Chain Daddy to Gemini CLI

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

{
  "mcpServers": {
    "mcp": {
      "httpUrl": "https://api.chaindaddy.io/mcp"
    }
  }
}

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

Chain Daddy will not start until these are set, so create_alert_rule never becomes available.

CHAINDADDY_API_KEY
CHAINDADDY_IAP_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 3 October 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.

Chain Daddy MCP server