Gemini CLI unesco-heritage-mcp-server unesco_search_sites
How to: Gemini CLI unesco-heritage-mcp-server unesco_search_sites
Add unesco-heritage-mcp-server to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"unesco-heritage-mcp-server": {
"httpUrl": "https://unesco-heritage.caseyjhand.com/mcp"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
Ask for something unesco_search_sites does. Gemini CLI lists the server's tools on connect and calls unesco_search_sites itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that unesco-heritage-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
unesco-heritage-mcp-server will not start until these are set, so unesco_search_sites never becomes available.
-
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.