For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Login
HomeDocsAPI ReferenceMCP ServerChat SDKsRelease Notes
HomeDocsAPI ReferenceMCP ServerChat SDKsRelease Notes
  • Introduction
    • Overview
    • Getting started
      • Claude Desktop
      • ChatGPT
      • Gemini CLI
      • Google ADK
      • Other MCP clients
      • Connecting multiple Agents
    • Authentication
    • Data privacy
    • Built-in prompts
    • FAQ
    • Troubleshooting
  • Tools
    • Overview
    • get_ada_configuration
    • get_ada_metric
    • get_available_filters
    • get_conversations
    • get_conversation
    • search_knowledge
    • search_coaching
    • get_improvement_guide
    • list_entities
    • propose_change
    • get_test_cases
    • get_test_runs
    • get_test_run_quota
    • send_feedback
  • Prompt library
    • Overview
    • Improvement recommendations
    • Quick health checks
    • Create visualizations
    • Diagnose performance issues
    • Identify optimization opportunities
    • Review configuration
    • Search knowledge and coaching
    • Test agent responses
    • Deep-dive analysis
Login
LogoLogo
On this page
  • Requirements
  • Option 1: OAuth (recommended)
  • Option 2: API key
IntroductionGetting started

Gemini CLI

Was this page helpful?
Previous

Google ADK

Next
Built with

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:

$npm install -g mcp-remote

Option 1: OAuth (recommended)

  1. Open your Gemini CLI settings file at ~/.gemini/settings.json.

  2. Add the following configuration under the existing mcpServers section (or create one if it does not exist):

    1{
    2 "mcpServers": {
    3 "ada": {
    4 "command": "npx",
    5 "args": ["mcp-remote", "https://acme-corp.ada.support/api/mcp/oauth"]
    6 }
    7 }
    8}
  3. Replace acme-corp.ada.support with your Ada instance domain. MCP routing is based on subdomain.

  4. Restart Gemini CLI.

  5. When you first attempt to use an Ada MCP tool, Gemini CLI detects the OAuth challenge from the server. If authentication is required, run:

    $/mcp auth ada

    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.

For security, prefer setting the API key as an environment variable outside of settings.json rather than pasting it directly into the file.
  1. Generate an API key from Config > PLATFORM > API keys in your Ada dashboard.

  2. Set the API key as an environment variable:

    $export ADA_API_KEY=your_api_key_here
  3. Open your Gemini CLI settings file at ~/.gemini/settings.json.

  4. Add the following configuration under the existing mcpServers section (or create one if it does not exist):

    1{
    2 "mcpServers": {
    3 "ada": {
    4 "command": "npx",
    5 "args": [
    6 "mcp-remote",
    7 "https://acme-corp.ada.support/api/mcp",
    8 "--header",
    9 "Authorization: Bearer ${ADA_API_KEY}"
    10 ]
    11 }
    12 }
    13}
  5. Replace acme-corp.ada.support with your Ada instance domain (see Authentication).

  6. Restart Gemini CLI.