Gemini CLI
Gemini CLI supports MCP server connections through its settings configuration. Both OAuth and API key authentication are supported.
Requirements
- Gemini CLI installed and configured with your Google account.
- Node.js LTS installed locally.
- An Agent, Admin, or Owner role in your Ada dashboard.
Gemini CLI uses the mcp-remote bridge to connect to HTTP-based MCP servers. If prompted, allow npx to install it automatically, or install it manually:
Option 1: OAuth (recommended)
-
Open your Gemini CLI settings file at
~/.gemini/settings.json. -
Add the following configuration under the existing
mcpServerssection (or create one if it does not exist): -
Replace
acme-corp.ada.supportwith your Ada instance domain. MCP routing is based on subdomain. -
Restart Gemini CLI.
-
When you first attempt to use an Ada MCP tool, Gemini CLI detects the OAuth challenge from the server. If authentication is required, run:
This opens a browser window to complete the OAuth login flow. After authentication completes, retry your request.
Option 2: API key
API key authentication uses a token generated from your Ada dashboard. This is useful for automated setups or when browser-based login is not available.
settings.json rather than pasting it directly into the file.-
Generate an API key from Config > PLATFORM > API keys in your Ada dashboard.
-
Set the API key as an environment variable:
-
Open your Gemini CLI settings file at
~/.gemini/settings.json. -
Add the following configuration under the existing
mcpServerssection (or create one if it does not exist): -
Replace
acme-corp.ada.supportwith your Ada instance domain (see Authentication). -
Restart Gemini CLI.