Connect Gemini CLI
ExperimentalThis integration has not passed a RateLoop release smoke test at a pinned client version.
Personal Google sign-in, including Google AI Pro and Ultra, stopped working in Gemini CLI on 18 June 2026. A Code Assist Standard/Enterprise license or a paid Gemini API key is required. Antigravity is a different client and has no recorded RateLoop test. JSON configuration uses httpUrl, not url plus type.
What to expect
- Sign in to Gemini CLI with a Code Assist Standard/Enterprise license or a paid Gemini API key
- Register the server with gemini mcp add
- Approve the RateLoop OAuth consent screen; use /mcp auth rateloop-workspace if needed
Connect your workspace
Copy your message from Connections and paste it into this app. It contains a private, single-use link. Keep the complete message private.
Example connection message
This example shows the instructions your agent receives. Its placeholder link cannot connect a workspace.
Connect this chat to my RateLoop workspace: call RateLoop's rateloop_connect_workspace tool once with the private link below. If no RateLoop tools are available, stop and tell me to add RateLoop first. Don't open, repeat or share the link. It works once. Check each answer with RateLoop and show its review status.
/connect/aci_...#...Host-native setup
Register at user scope, then run /mcp auth rateloop-workspace if prompted
gemini mcp add --scope user --transport http rateloop-workspace https://www.rateloop.ai/api/agent/v1/mcpChecked 2026-07-17 against provider-docs-snapshot@2026-07-17.
settings.json entry; the transport field is httpUrl, not url plus type
{
"mcpServers": {
"rateloop-workspace": {
"httpUrl": "https://www.rateloop.ai/api/agent/v1/mcp"
}
}
}Checked 2026-07-17 against provider-docs-snapshot@2026-07-17.
Check and recover
The connection is ready only after rateloop_connect_workspace or rateloop_verify_connection verifies it. If tools are missing, check the app's server setup and policy. After access expires or is revoked, complete the app's OAuth prompt, then create a targeted reconnect message in Connections (or a new message if the agent was deleted). Never reuse a claimed link. Recovery guide.
Delivery controls remain advisory; your workflow decides when to send an output.