Gemini CLI Countersign by Signalry request_agent_key
How to: Gemini CLI Countersign by Signalry request_agent_key
Add Countersign by Signalry to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"countersign": {
"httpUrl": "https://countersign.signalry.ai/mcp?ref=mcp-registry"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
Ask for something request_agent_key does. Gemini CLI lists the server's tools on connect and calls request_agent_key itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Countersign by Signalry'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 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.