Gemini CLI market pulse pulse_stats

How to: Gemini CLI market pulse pulse_stats

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

Add market pulse to Gemini CLI

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

{
  "mcpServers": {
    "market-pulse": {
      "httpUrl": "https://market-pulse.t3ratech.co.zw/mcp"
    }
  }
}

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

market pulse will not start until these are set, so pulse_stats never becomes available.

MARKET_PULSE_API_KEY
MARKET_PULSE_TIMEOUT_MS

Same tool, other clients

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

market pulse MCP server