How to integrate Kadoa MCP with Google ADK

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Kadoa logo
Google ADK logo
divider

Introduction

This guide walks you through connecting Kadoa to Google ADK using the Composio tool router. By the end, you'll have a working Kadoa agent that can fetch the latest data from your workflow, check crawl status for session abc123, list all pages crawled in last run through natural language commands.

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

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

Also integrate Kadoa with

TL;DR

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

The Kadoa MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Kadoa account. It provides structured and secure access to your data extraction workflows, so your agent can launch crawls, monitor sessions, retrieve extracted data, and manage workflow configurations automatically on your behalf.

  • Automated workflow monitoring and management: Ask your agent to fetch workflow configurations, enable data validation, or get the latest results from any extraction workflow you have set up.
  • Crawling session control: Have your agent check the status of crawl sessions, list all crawled pages, and pull the raw content (HTML or Markdown) from any page processed by a workflow.
  • Notification channel setup and retrieval: Direct your agent to create notification channels, list available notification event types, and fetch specific channel configurations for streamlined alerting.
  • Location and environment awareness: Let your agent retrieve all supported locations to ensure workflows run in the right environment before launching new extraction jobs.
  • Seamless data access: Instruct your agent to quickly get the most recent data output from any workflow, keeping your automations and dashboards always up to date.

Supported Tools & Triggers

Tools
Bulk Approve Validation RulesTool to bulk approve preview validation rules for a workflow.
Create Crawl ConfigTool to create a new crawling configuration in Kadoa.
Create Notification ChannelTool to create a notification channel for alerts delivery.
Create SchemaCreate a new data schema with specified fields and entity type.
Create Support IssueTool to create a support ticket in Kadoa.
Create Workflow TriggerTool to create a trigger that fires when a source workflow emits an event.
Delete All Validation RulesTool to soft-delete all validation rules for a specific workflow with optional audit trail.
Delete Crawl ConfigurationTool to delete a crawling configuration by its config ID.
Delete Notification ChannelTool to delete a notification channel by its ID.
Delete SchemaTool to delete a schema and all its revisions.
Delete Validation RuleTool to delete a validation rule from a Kadoa workflow.
Delete Validation Rules (Bulk)Tool to bulk delete multiple validation rules for a workflow.
Delete WorkflowDelete a workflow permanently from your Kadoa account.
Delete Workflow TriggerTool to delete a trigger from a Kadoa workflow.
Disable Validation RuleTool to disable a validation rule with a mandatory reason.
Enable Data ValidationTool to enable data validation on a specified workflow.
Execute Bulk Workflow OperationsExecute actions on multiple workflows at once.
Export Activity EventsTool to export activity events from audit logs to CSV format for compliance and audit purposes.
Export Activity WorkflowsTool to export workflow configurations and metadata as CSV for portfolio reviews and compliance reporting.
Get Workflow by IDRetrieve detailed configuration of a workflow by its ID.
Get all locationsRetrieves all available scraping proxy locations (countries) supported by Kadoa.
Get Crawl Bucket DataTool to retrieve file content from the Kadoa crawling bucket (HTML or screenshot).
Get Crawl ConfigurationTool to retrieve a crawling configuration by its ID.
Get Crawled Page ContentTool to retrieve content of a crawled page.
Get Crawled PagesTool to list pages crawled during a session.
Get Crawl StatusTool to fetch current status of a crawling session.
Get Event Type DetailsTool to retrieve details for a specific notification event type.
Get Notification Event TypesTool to retrieve supported notification event types.
Get Latest Workflow DataRetrieves the extracted data from a Kadoa workflow's most recent run (or a specific run if runId is provided).
Get Latest Workflow ValidationRetrieves the latest validation results for the most recent job of a workflow.
Get Notification ChannelTool to retrieve details of a specific notification channel.
Get Notification LogsTool to retrieve notification event logs with optional filtering by workflow, event type, and date range.
Get Notification SettingRetrieves a specific notification setting by its unique identifier.
Get Schema by IDRetrieve a specific schema by its unique identifier.
Get Validation AnomaliesTool to retrieve all anomalies for a specific validation.
Get Validation Anomalies By RuleTool to retrieve anomalies for a specific validation rule.
Get Validation ConfigurationTool to retrieve the data validation configuration for a specific workflow.
Get Validation RuleTool to retrieve a specific validation rule by its ID.
Get Workflow Audit LogRetrieve audit log entries for a workflow.
Get Workflow JobTool to retrieve the current status and telemetry information for a specific workflow job.
Get Workflow Run HistoryTool to fetch workflow run history.
Get WorkflowsRetrieve a paginated list of workflows with optional filtering.
Get Workflow TriggerTool to retrieve a specific trigger for a workflow.
Get Workflow Validation ResultsRetrieves the latest validation results for a specific workflow job.
Get Workspace DetailsTool to retrieve detailed information about a workspace (user, team, or organization).
List Activity EventsTool to retrieve activity events from audit logs with basic filtering and pagination.
List ChangesTool to retrieve all data changes detected across workflows in your Kadoa account.
List Crawl SessionsTool to retrieve a paginated list of crawling sessions with optional filtering.
List Job ValidationsTool to list all validation runs for a specific job with pagination support.
List Notification ChannelsTool to retrieve all notification channels configured for the account.
List Notification SettingsTool to retrieve all notification settings, with optional filtering by workflow ID or event type.
List SchemasTool to retrieve all schemas accessible by the authenticated user.
List Support StatesTool to retrieve available support issue states.
List Validation RulesTool to list all data validation rules with optional pagination and filtering.
List Workflow TriggersTool to get all triggers where the specified workflow is the source.
Pause Crawl SessionTool to pause an active crawling session.
Pause WorkflowTool to pause a running or scheduled workflow.
Create Advanced WorkflowTool to create an advanced workflow.
Start Crawl SessionStarts a new web crawling session to crawl and index pages from a website.
Create Notification SettingTool to create a notification setting linking channels to events.
Send Test NotificationSends a test notification event to verify notification channel configurations are working correctly.
Subscribe to Webhook EventsTool to subscribe to specified webhook events.
Create WorkflowCreate a new Kadoa web scraping workflow.
Configure Workflow MonitoringConfigure monitoring and scheduling for a Kadoa workflow to detect data changes.
Generate Workflow Validation RuleGenerate an AI-powered data validation rule for a Kadoa workflow.
Update Notification ChannelTool to update an existing notification channel.
Resume Crawl SessionTool to resume a paused crawling session.
Resume WorkflowResumes a paused, preview, or error workflow.
Run Ad-hoc ExtractionTool to synchronously extract data from a URL using a given template.
Run WorkflowTool to trigger a workflow to run immediately.
Schedule Validation JobTool to schedule a data validation job for a specific workflow job.
Unsubscribe from Webhook EventsUnsubscribe from webhook event notifications by deleting a notification setting.
Update Notification SettingsTool to update existing notification settings for events.
Update SchemaTool to update an existing Kadoa schema.
Update Validation ConfigurationTool to update the complete data validation configuration including alerting settings for a specific workflow.
Update Workflow MetadataTool to update workflow metadata such as name, description, tags, and configuration settings.
Update Workflow TriggerTool to update trigger properties including event type and enabled status.

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

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

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.

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 Kadoa via MCP
  • python-dotenv loads environment variables

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

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

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

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

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

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 Kadoa 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

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 Kadoa 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=["kadoa"],
)

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

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

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Kadoa 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.

How to build Kadoa MCP Agent with another framework

FAQ

What are the differences in Tool Router MCP and Kadoa MCP?

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

Can I use Tool Router MCP with Google ADK?

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 Kadoa tools.

Can I manage the permissions and scopes for Kadoa while using Tool Router?

Yes, absolutely. You can configure which Kadoa 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.

How safe is my data with Composio Tool Router?

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 Kadoa data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.