Skip to content

Gemini CLI Fetch Router fetch_page

How to: Gemini CLI Fetch Router fetch_page

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

Add Fetch Router to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "fetchrouter-mcp": {
      "httpUrl": "https://fetchrouter.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    Ask for something fetch_page does. Gemini CLI lists the server's tools on connect and calls fetch_page itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Fetch Router'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

Fetch Router will not start until these are set, so fetch_page never becomes available.

  • FETCHROUTER_API_KEY

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.