Gemini CLI adds Looker extensions

4. Configure Your Looker connection:

After installation, you’ll need to configure the extensions to connect to your Looker instance. You’ll need a Looker Client ID and Client Secret, which can be obtained by following the instructions in the Looker API authentication documentation. If you don’t have access to the Admin pages of the Looker system, ask your administrator to get the ID and Secret for you.

Then set the following environment variables before starting the Gemini CLI. These variables can also be loaded from a .env file.

• LOOKER_BASE_URL: The base URL of your Looker instance (e.g., https://looker.example.com). In some cases, you may need to add :19999 to the URL.

• LOOKER_CLIENT_ID: The Looker API client ID

• LOOKER_CLIENT_SECRET: The Looker API client secret

• LOOKER_VERIFY_SSL: (Optional) Whether to verify SSL certificates. Defaults to true

For looker-conversational-analytics, you also need to provide application default credentials with the correct roles as well as a GCP project with the proper APIs enabled. See https://googleapis.github.io/genai-toolbox/resources/sources/looker/ for all the details. In addition, you need to define these environment variables:

• LOOKER_PROJECT: The Google Cloud Project to use

• LOOKER_LOCATION: The Google Cloud Location to use, such as us

Dive deeper

The release of these new extensions is a valuable milestone in our efforts to bring the full benefits of Gemini and Looker together for you. To help you get the most out of these new extensions, we’ve prepared relevant documentation within MCP Toolbox. These resources provide detailed information on all the available tools and functionality.

We welcome your feedback as we continue to innovate. Get started today and unlock the full potential of your data.