How to integrate Openlayer MCP with Google ADK

This guide walks you through connecting Openlayer to Google ADK using the Composio tool router. By the end, you'll have a working Openlayer agent that can list your projects, inspect project versions, review test results, find failing tests, and check data sources through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Openlayer account through Composio's Openlayer MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Openlayer logoOpenlayer
Api Key

Openlayer is an AI quality platform for managing projects, monitoring production data, evaluating tests, and inspecting model performance. Use it to catch regressions, track production quality, and keep AI applications reliable before and after release.

10 Tools

Introduction

This guide walks you through connecting Openlayer to Google ADK using the Composio tool router. By the end, you'll have a working Openlayer agent that can list your projects, inspect project versions, review test results, find failing tests, and check data sources through natural language commands.

This guide will help you understand how to give your Google ADK agent real control over a Openlayer account through Composio's Openlayer MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Openlayer with

TL;DR

Here's what you'll learn:
  • Get a Openlayer account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Openlayer
  • Build an agent that connects to Openlayer through MCP
  • Interact with Openlayer using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

What is the Openlayer MCP server, and what's possible with it?

The Openlayer MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Openlayer account. It provides structured and secure access to your projects, versions, monitoring data sources, tests, results, and workspace details, so your agent can review projects, inspect model versions, check monitoring status, analyze test outcomes, and track workspace usage on your behalf.

  • Project and version reviews: Have your agent list Openlayer projects, inspect their versions, and compare processing status and passing, failing, and total test counts.
  • Production monitoring checks: Let the agent find monitoring data sources and review their backend, monitoring status, record counts, and test counts.
  • Test configuration discovery: Direct your agent to list tests for a project and narrow them by category, archive state, origin, production data use, or suggested status.
  • Test result analysis: Instruct your agent to review results for project versions, monitoring data sources, or individual tests, including execution status and available generated insights.
  • Workspace usage visibility: Have your agent check workspace status, connected account membership, usage counts, and current plan limits.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step09 STEPS
1

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python
2

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.
3

Install dependencies

bash
pip install google-adk composio python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Openlayer via MCP
  • python-dotenv loads environment variables
4

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file
5

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management
6

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP
7

Create Composio client and Tool Router session

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["openlayer"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url,
print(f"Composio MCP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration
8

Set up the McpToolset and create the Agent

python
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Openlayer operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls
9

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web

Execute the agent from the project root. The web command opens a web portal where you can chat with the agent.

What's happening:

  • adk run runs the agent in CLI mode
  • adk web . opens a web UI for interactive testing

Complete Code

Here's the complete code to get you started with Openlayer and Google ADK:

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()
warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["openlayer"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url


composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": COMPOSIO_API_KEY}
    )
)

root_agent = Agent(
    model="gemini-2.5-flash",
    name="composio_agent",
    description="An agent that uses Composio tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Openlayer operations."
    ),  
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")

Conclusion

You've successfully integrated Openlayer with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Openlayer using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Openlayer tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

TOOLS

Supported Tools

Every Openlayer action and event your agent gets out of the box.

Get Data Source

Return one Openlayer monitoring data source, including its backend, monitoring status, record and test counts, and optional project or workspace details.

Get Project Version

Return one Openlayer project commit or version with its processing status, commit metadata, storage URI, and passing, failing, and total test counts.

Get Workspace

Return a workspace's identity, status, connected-account membership, usage counts, and plan limits.

List Data Sources

Return one page of monitoring data sources for an Openlayer project, optionally filtered by name.

List Data Source Test Results

Return one page of the latest monitoring test results for an Openlayer data source, optionally filtered by test category or execution status.

List Projects

Return one page of projects visible to the connected Openlayer workspace, optionally filtered by name or task type.

List Project Versions

Return one page of commits and versions for an Openlayer project, including processing status, commit metadata, and passing, failing, and total test counts.

List Project Version Test Results

Return one page of test results for a project version, optionally filtered by test category, archive state, or result status.

List Test Results

Return one page of results for a test, with optional project-version, data-source, and status filters and optional generated insights.

List Tests

Return one page of tests configured for an Openlayer project, with filters for category, archive state, origin version, production-data use, and suggested status.

FAQ

Frequently asked questions

With a standalone Openlayer MCP server, the agents and LLMs can only access a fixed set of Openlayer tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Openlayer and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Google ADK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Openlayer tools.

Yes, absolutely. You can configure which Openlayer scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Openlayer data and credentials are handled as safely as possible.

Start with Openlayer.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Openlayer tool your agent needs.Free to start.

Start building