How to integrate Jam MCP with Google ADK

This guide walks you through connecting Jam to Google ADK using the Composio tool router. By the end, you'll have a working Jam agent that can list your bug reports, analyze videos, inspect console logs, trace network requests, and read transcripts through natural language commands. This guide will help you understand how to give your Google ADK agent real control over a Jam account through Composio's Jam MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Jam logoJam
Api Key

Jam is a browser bug reporting and recording platform for capturing issues, console logs, network data, and repro context. Teams use Jam to inspect, organize, and collaborate on bugs faster without long back-and-forth threads.

16 Tools

Introduction

This guide walks you through connecting Jam to Google ADK using the Composio tool router. By the end, you'll have a working Jam agent that can list your bug reports, analyze videos, inspect console logs, trace network requests, and read transcripts through natural language commands.

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

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

Also integrate Jam with

TL;DR

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

The Jam MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Jam account. It provides structured and secure access to your browser bug reports, recordings, and debugging context, so your agent can analyze reported issues, inspect technical evidence, trace user interactions, review visual details, and browse workspace content on your behalf.

  • Bug report investigation: Have your agent review a Jam’s core details, reported issue, user goal, feedback, and technical indicators to understand what went wrong.
  • Console and network analysis: Let the agent inspect console messages, stack traces, failed network requests, HTTP traffic, and WebSocket activity captured with a Jam.
  • User journey reconstruction: Direct your agent to trace clicks, form inputs, submissions, navigation, and scrolling in chronological order.
  • Recording and screenshot review: Instruct your agent to examine screenshots, sample video frames, analyze recordings, and read available speech transcripts for visual and spoken context.
  • Workspace discovery: Have your agent search Jams, folders, members, recording links, submitted reports, and connected recording domains across your workspace.

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 Jam 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=["jam"],
)

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 Jam 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 Jam 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=["jam"],
)

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

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

Conclusion

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

Key takeaways:

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

Analyze Jam Video

Extract structured user goals, reported issues, feedback, visual observations, interactions, and technical indicators from a video Jam.

Get Console Logs

Get captured browser console errors, warnings, information, debug output, and stack traces from a Jam.

Get Jam Details

Get the core details and debugging context for a Jam.

Get Jam Metadata

Get custom application debugging context attached through the jam.

Get Network Requests

Get captured HTTP requests and WebSocket frames from a Jam, with filters for failures, hosts, methods, content types, and response bodies.

Get Recording Link

Get one Recording Link's settings and submitted-Jam count by public ID.

Get Jam Screenshots

Get screenshots and image attachments from a screenshot-type Jam for visual inspection.

Get User Events

Get the chronological user interaction timeline from a Jam, including clicks, inputs, submissions, navigation, and scrolling.

Get Jam Video Frames

Get still frames from a video Jam as an overview grid, exact timestamps, or an evenly sampled time window.

Get Jam Video Transcript

Get the timestamped WebVTT speech transcript from a microphone-enabled video Jam when available; otherwise return Jam's explanation that it is pending or unavailable.

List Jam Folders

Browse or search one page of workspace folders and return their IDs, names, Jam counts, and timestamps; pass next_cursor as cursor to continue.

List Jams

Search and browse workspace Jams by text, type, folder, author, source URL, or creation date.

List Jam Members

Browse or search one page of workspace members by name or email for author discovery and attribution; pass next_cursor as cursor to continue.

List Recording Domains

List the workspace's connected recording domains and whether each is verified to capture console and network logs.

List Recording Link Jams

List Jams submitted through one Recording Link, newest first.

List Recording Links

List workspace Recording Links newest first, optionally including revoked links.

FAQ

Frequently asked questions

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

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

Start with Jam.It takes 30 seconds.

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

Start building