Gemini CLI trading signals mcp opening_range

How to: Gemini CLI trading signals mcp opening_range

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

Add trading signals mcp to Gemini CLI

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

{
  "mcpServers": {
    "trading-signals-mcp": {
      "httpUrl": "https://signals.incomefather.com/mcp"
    }
  }
}

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

trading signals mcp will not start until these are set, so opening_range never becomes available.

X402_PRIVATE_KEY
MAX_USD_PER_CALL
TRADING_SIGNALS_BASE_URL

Same tool, other clients

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

trading signals mcp MCP server