Skip to content
mcp/harbor

Gemini CLI norway location transport mcp get_departures

How to: Gemini CLI norway location transport mcp get_departures

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

Add norway location transport mcp to Gemini CLI

  1. 01

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

{
  "mcpServers": {
    "norway-location-transport-mcp": {
      "httpUrl": "https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

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

  3. 04

    If nothing happens, check the server is running and that norway location transport 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

norway location transport mcp will not start until these are set, so get_departures never becomes available.

  • ET_CLIENT_NAME

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.

norway location transport mcp MCP server