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