How to integrate Arize AX MCP with Google ADK

This guide walks you through connecting Arize AX to Google ADK using the Composio tool router. By the end, you'll have a working Arize AX agent that can summarize failed spans from latest traces, compare experiment results across prompt versions, create dataset from production traces through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Arize AX account through Composio's Arize AX MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Arize AX logoArize AX
Api Key

Arize AX is an AI engineering platform for tracing, evaluating, and improving AI applications. Use it to debug LLM behavior, compare experiments, and improve production AI quality.

24 Tools

Introduction

This guide walks you through connecting Arize AX to Google ADK using the Composio tool router. By the end, you'll have a working Arize AX agent that can summarize failed spans from latest traces, compare experiment results across prompt versions, create dataset from production traces through natural language commands.

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

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

Also integrate Arize AX with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLILangChainVercel AI SDKMastra AILlamaIndexCrewAI

TL;DR

Here's what you'll learn:
  • Get a Arize AX account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Arize AX
  • Build an agent that connects to Arize AX through MCP
  • Interact with Arize AX 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 Arize AX MCP server, and what's possible with it?

The Arize AX MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Arize AX account. It provides structured and secure access to your projects, datasets, prompts, experiments, traces, and spans, so your agent can inspect AI activity, manage evaluation data, maintain prompts, run experiments, and review results on your behalf.

  • Project and space discovery: Have your agent find accessible spaces and projects, then retrieve details about the AI applications you monitor.
  • Dataset management: Let the agent create and rename datasets, add or update examples, and review examples from current or named dataset versions.
  • Prompt versioning: Direct your agent to create prompts, publish new immutable versions, update prompt descriptions, and review current or previous versions.
  • Experiment tracking: Instruct your agent to create experiments, append runs, and inspect experiment outputs for evaluation and comparison.
  • Trace and span analysis: Have your agent review bounded sets of traces and spans within chosen time ranges and filters to investigate application behavior.

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 Arize AX 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=["arize_ax"],
)

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 Arize AX 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 Arize AX 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=["arize_ax"],
)

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 Arize AX operations."
    ),  
    tools=[composio_toolset],
)

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Arize AX 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 Arize AX action and event your agent gets out of the box.

Add Dataset Examples

Append arbitrary-field examples to an Arize dataset or a specified dataset version.

Add Experiment Runs

Append one or more runs to an existing Arize experiment.

Create Dataset

Create an Arize dataset in a space with an explicit initial array of examples.

Create Experiment

Create an Arize experiment with initial runs, associated with exactly one dataset or space.

Create Prompt

Create an Arize prompt and its initial version in a space.

Create Prompt Version

Create a new immutable version of an existing Arize prompt.

Get Dataset

Get one Arize dataset and its versions by dataset ID.

Get Experiment

Get one Arize experiment by its ID, without its experiment runs.

Get Project

Get one accessible Arize project by its ID.

Get Prompt

Get an Arize prompt with its current, explicitly selected, or labeled version.

Get Space

Get one accessible Arize space by its ID.

List Dataset Examples

List one page of examples from an Arize dataset or a specific dataset version, preserving user-defined example fields.

List Datasets

List one page of Arize datasets, optionally filtered by space or dataset name.

List Experiment Runs

List one page of runs and outputs for an Arize experiment, preserving additional run fields.

List Experiments

List one page of Arize experiments, optionally filtered by dataset, space, or name.

List Projects

List one page of accessible Arize projects, optionally filtered by space or project name.

List Prompts

List one page of Arize prompts, optionally filtered by space or prompt name.

List Prompt Versions

List one page of versions for an Arize prompt, newest first.

List Spaces

List one page of Arize spaces accessible to the connected API key, optionally filtered by organization or name.

List Spans

Read one bounded page of spans for an Arize project using optional time and filter constraints.

List Traces

Read one bounded page of traces and nested spans for an Arize project using optional time and filter constraints; nested spans may be truncated per trace.

Update Dataset

Rename an existing Arize dataset.

Update Dataset Examples

Update existing Arize dataset examples by ID, optionally creating a named dataset version.

Update Prompt

Update or clear an Arize prompt's description.

FRAMEWORKS

How to build Arize AX MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Arize AX MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Arize AX MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Arize AX MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Arize AX MCP with Claude Cowork

Codex logo

Codex

Use Arize AX MCP with Codex

OpenClaw logo

OpenClaw

Use Arize AX MCP with OpenClaw

Hermes logo

Hermes

Use Arize AX MCP with Hermes

CLI logo

CLI

Use Arize AX MCP with CLI

LangChain logo

LangChain

Use Arize AX MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Arize AX MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Arize AX MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Arize AX MCP with LlamaIndex

CrewAI logo

CrewAI

Use Arize AX MCP with CrewAI

FAQ

Frequently asked questions

With a standalone Arize AX MCP server, the agents and LLMs can only access a fixed set of Arize AX tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Arize AX 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 Arize AX tools.

Yes, absolutely. You can configure which Arize AX 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 Arize AX data and credentials are handled as safely as possible.

Start with Arize AX.It takes 30 seconds.

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

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies