Connect Gemini CLI to Agent Authority

When you finish, every MCP tool call Gemini CLI makes is checked against your policies and recorded in the audit log. Google's Gemini CLI reaches your approved tools through one SecureAuth Agent Authority gateway URL, and each developer signs in as themselves.

SetupCopy Anchor Link

1. Add the MCP server. Add the following to ~/.gemini/settings.json:

   Copy Text

   {
     "mcpServers": {
       "secureauth": {
         "url": "https://your-gateway-url/gateway/mcp",
         "type": "http",
         "oauth": {
           "scopes": ["mcp_gateway", "profile", "email"]
         }
       }
     }
   }

2. Authenticate. Start Gemini CLI (gemini), then type /mcp auth secureauth. A browser window opens for sign-in.

3. Start using. Gemini CLI picks up the tools on the next turn.

   The agent is auto-registered on first connect.

Connecting to just one MCP? To stay under an agent's tool limit, point the URL at a single MCP — /gateway/mcp/{slug} instead of /gateway/mcp. Grab the exact URL from the resource's detail page; see Scope a connection.

Next stepsCopy Anchor Link

• Create a policy – control which tools Gemini CLI can call.
• Monitor activity – watch its tool calls appear in the dashboard and audit log.
• Audit log – filter and search every tool call Gemini CLI makes.