Gemini CLI RanklyBee update_lead_monitor

How to: Gemini CLI RanklyBee update_lead_monitor

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

Add RanklyBee to Gemini CLI

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

{
  "mcpServers": {
    "ranklybee": {
      "httpUrl": "https://api.ranklybee.com/mcp"
    }
  }
}

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

Same tool, other clients

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

RanklyBee MCP server