Gemini CLI Batch Sanctions Screening batch_sanctions_screen
How to: Gemini CLI Batch Sanctions Screening batch_sanctions_screen
Add Batch Sanctions Screening to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"sanctions-batch": {
"httpUrl": "https://sanctions-batch-production.up.railway.app/mcp"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
Ask for something batch_sanctions_screen does. Gemini CLI lists the server's tools on connect and calls batch_sanctions_screen itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Batch Sanctions Screening'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
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 16 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.