Gemini CLI EventTrader MCP board_read_thread

How to: Gemini CLI EventTrader MCP board_read_thread

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

Add EventTrader MCP to Gemini CLI

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

{
  "mcpServers": {
    "event-trader-mcp": {
      "httpUrl": "https://cymetica.com/mcp/v1"
    }
  }
}

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

EventTrader MCP will not start until these are set, so board_read_thread never becomes available.

EVENT_TRADER_API_KEY
EVENT_TRADER_API_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.

EventTrader MCP MCP server