Gemini CLI LiquiLens — the Failure Radar Prompt/crypto_liquidity_briefing
How to: Gemini CLI LiquiLens — the Failure Radar crypto_liquidity_briefing
Add LiquiLens — the Failure Radar to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"liquilens": {
"httpUrl": "https://api.liquilens.in/mcp"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
crypto_liquidity_briefing is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Gemini CLI will not call it for you.
-
04
If it does not appear, check that LiquiLens — the Failure Radar is connected and that you are looking at its prompts rather than its tools.
Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs
Same prompt, other clients
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.