How to connect Looker to Gemini Enterprise in minutes, with MCP Toolbox and ADK

We can all agree that the quality of AI-driven answers relies on the consistency of the underlying data. But AI models, while powerful, lack business context out of the box. As more organizations ask questions of their data using natural language, it is increasingly important to unify business measures and dimensions, ensure consistency company-wide. If you want trustworthy AI, what you need is a semantic layer that acts as the single source of truth for business metrics.But how do you make that data accessible and actionable for your end users? Building off the recent introduction of Looker’s Model Context Protocol (MCP) server, in this blog we take you through the process of creating an Ag…

MCP Toolbox for Databases is a central open-source server that hosts and manages toolsets, enabling agentic applications to leverage Looker’s capabilities without working directly with the platform. Instead of managing tool logic and authentication themselves, agents act as MCP clients and request tools from the Toolbox. The MCP Toolbox handles all the underlying complexities, including secure connections to Looker, authentication and query execution.

The MCP Toolbox for Databases natively supports Looker’s pre-built toolset. To access these tools, follow the below steps:

Connect to Cloud Shell. Check that you’re already authenticated, and that the project is set to your project ID using the following command:

Run the following command in Cloud Shell to confirm that the gcloud command knows about your project:

Create a folder named mcp-toolbox:

Go to the mcp-toolbox folder via the command shown below:

Install the binary version of the MCP Toolbox for Databases via the script given below. This command is for Linux; if you run on Macintosh or Windows, ensure that you download the correct binary. Check out the releases page for your Operation System and Architecture and download the correct binary.

Deploy Toolbox to Cloud Run

Next, you’ll need to run MCP Toolbox. The simplest way to do that is on Cloud Run, Google Cloud’s fully managed container application platform. Here’s how:

Enable relevant APIs if needed:

Create a service account and assign necessary roles:

Export the toolbox config into an image variable:

Deploy MCP Toolbox to Cloud Run:

The Cloud Run will ask if you want Unauthenticated, select No.Allow Unauthenticated: N

Step 2: Deploy ADK Agent to Agent Engine

Next, you need to configure Agent Development Kit (ADK), a flexible and modular framework for developing and deploying AI agents. ADK was designed to make agent development feel more like software development, to make it easier for developers to create, deploy, and orchestrate agentic architectures that range from simple tasks to complex workflows. And while ADK is optimized for Gemini and the Google ecosystem, it’s also model-agnostic, deployment-agnostic, and is built for compatibility with other frameworks.

Vertex AI Agent Engine, a part of the Vertex AI Platform, is a set of services that enables developers to deploy, manage, and scale AI agents in production. Agent Engine handles the infrastructure to scale agents in production so you can focus on creating applications.

Open a new terminal tab in Cloud Shell and create a folder named my-agents as follows. You also need to navigate to the my-agents folder.

Now, create a virtual Python environment using venv:

Activate the virtual environment:

Install the ADK and the MCP Toolbox for Databases packages along with langchain dependency:

Creating your first Agent Application

Now you’re ready to use adk to create a scaffolding, including folders, environment and basic files, for our Looker Agent Application via the adk create command with an app name looker_app:

Follow the steps and select the following:

Gemini model for choosing a model for the root agent

Vertex AI for the backend

Your default Google Project Id and region

Observe the folder in which a default template and required files for the Agent have been created.

First up is the .env file:

The values indicate that you will be using Gemini via Vertex AI along with the respective values for the Google Cloud Project Id and location.

Then you have the __init__.py file that marks the folder as a module and has a single statement that imports the agent from the agent.py file:

Finally, take a look at the agent.py file. The contents can be edited to similar to the example below:

Insert the Cloud Run URL highlighted here (. not the one with the project number in the url).

Create a Cloud Storage bucket if necessary:

Ensure you are in the my-agents directory. Update the BUCKET_NAME with the Cloud Storage bucket you want to use:

NOTE: Ensure you grant the Cloud Run Invoker role to the default Agent Engine Service Account (i.e., service-PROJECT_NUMBER@gcp-sa-aiplatform-re.iam.gserviceaccount.com)

Step 3: Connect to Gemini Enterprise

Now it’s time to create a Gemini Enterprise app (instructions here).

Run the below command with the GCP Project Number, Reasoning Engine resource name output from the ‘deploy agent_engine’ command above, and your Gemini Enterprise Agent ID from the Gemini Enterprise Apps interface:

Your Looker data will now be available within your Gemini Enterprise app.If you don’t have access to this feature, contact your Google Cloud account team.

Querying business data made easier

Connecting Looker’s semantic layer to Vertex AI Agent services by way of the ADK and MCP Toolbox is a big win for data accessibility. By exposing your trusted Looker models and Explores in Gemini Enterprise, you empower end-users to query complex business data using natural language. This integration closes the gap between data insights and immediate action, ensuring that your organization’s semantic layer is not just a source of passive reports, but an active, conversational, and decision-driving asset.

To get started, connect to the MCP Toolbox for Databases on GitHub and set up Looker integration.

Posted in