Gemini CLI geonames-mcp-server geonames_reverse_geocode

How to: Gemini CLI geonames-mcp-server geonames_reverse_geocode

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

Add geonames-mcp-server to Gemini CLI

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

{
  "mcpServers": {
    "geonames-mcp-server": {
      "httpUrl": "https://geonames.caseyjhand.com/mcp"
    }
  }
}

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

geonames-mcp-server will not start until these are set, so geonames_reverse_geocode never becomes available.

GEONAMES_USERNAME
MCP_LOG_LEVEL

Same tool, other clients

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

geonames-mcp-server MCP server