security engineer for Gemini CLI
io.github.guardbee/security-engineer
Fix GuardBee AI Security Engineer findings in your repo with your coding agent, then verify
client:Gemini CLI
transport:stdio
runtime:npm
Install security engineer in Gemini CLI
~/.gemini/settings.json · windows: %USERPROFILE%\.gemini\settings.json
{
"mcpServers": {
"security-engineer": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-security-engineer"
],
"env": {
"GUARDBEE_API_KEY": "<GUARDBEE_API_KEY>"
}
}
}
}
Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs