How to integrate Clickmeeting MCP with Google ADK

Framework Integration Gradient
Clickmeeting Logo
Google ADK Logo
divider

Introduction

This guide walks you through connecting Clickmeeting to Google ADK using the Composio tool router. By the end, you'll have a working Clickmeeting agent that can schedule a new webinar for next week, add attendee to upcoming training session, generate pdf report for yesterday's session, list all chat conversations from last conference through natural language commands.

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

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

TL;DR

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

The Clickmeeting MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Clickmeeting account. It provides structured and secure access to your webinars and meetings, so your agent can perform actions like scheduling conferences, managing contacts, generating reports, handling recordings, and more—all on your behalf.

  • Automated conference creation and scheduling: Seamlessly instruct your agent to create new meetings or webinars, helping you organize virtual events in seconds.
  • Contact management and attendee registration: Have your agent add or pre-register participants as contacts before scheduling or starting events, ensuring a smooth entry process.
  • Recording management and cleanup: Direct your agent to delete specific recordings or clear all session recordings for a conference room, keeping your account tidy and compliant.
  • Instant session analytics and reporting: Ask your agent to generate detailed PDF reports for any session, so you can quickly access valuable insights and analytics.
  • Easy access and participation links: Let your agent generate autologin URLs for participants, allowing direct, hassle-free entry to your meetings without manual logins.

Supported Tools & Triggers

Tools
Create ConferenceTool to create a new conference.
Create ContactTool to create a new contact in your clickmeeting account.
Delete ConferenceTool to delete a specific conference.
Delete RecordingTool to delete a specific recording for a conference room.
Delete RecordingsTool to delete all recordings for a conference room.
Generate Autologin URLTool to generate an autologin url for a conference participant.
Generate Session PDF ReportTool to generate a pdf report for a specific session.
Get Chat DetailsTool to retrieve details of a specific chat session.
Get ChatsTool to retrieve a list of all chat sessions.
Get Conference DetailsTool to retrieve details of a specific conference.
Get Conference FilesTool to retrieve files associated with a conference.
Get ConferencesTool to retrieve a paginated list of conference rooms.
Get Conference SessionsTool to retrieve a list of sessions for a conference room.
Get Conference SkinsTool to retrieve a list of available conference room skins.
Get File LibraryTool to retrieve a list of files in the file library.
Get Phone GatewaysTool to retrieve a list of available phone gateways.
Ping APITool to check api service status.
Get RecordingsTool to retrieve recordings for a specific conference room.
Get RegistrationsTool to retrieve registrations for a conference room by status.
Get Session Attendee DetailsTool to retrieve details of a specific session attendee.
Get Session AttendeesTool to retrieve the attendee list for a specific session.
Get Session DetailsTool to retrieve details of a specific session in a conference room.
Get Session Poll DetailsTool to retrieve details of a specific poll conducted during a session.
Get Session PollsTool to retrieve a list of polls conducted during a specific session.
Get Session Q&A HistoryTool to retrieve the q&a history for a specific session.
Get Session Recording DetailsTool to retrieve details of a specific recording for a session.
Get Session RecordingsTool to retrieve a list of recordings for a specific session.
Get Session RegistrationsTool to retrieve registrations for a specific session.
Get Session Survey DetailsTool to retrieve details of a specific survey conducted during a session.
Get Session SurveysTool to retrieve a list of surveys conducted during a specific session.
Get Time Zone ListTool to retrieve a list of available time zones.
Get Time Zone List by CountryTool to retrieve time zones for a specific country.
Register ParticipantTool to register a participant for a conference room.
Send InvitationTool to send invitation emails to a clickmeeting conference.
Send Invitation EmailTool to send invitation emails to participants of a clickmeeting conference.
Upload FileTool to upload a new file to the file library.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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-google 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 Clickmeeting via MCP
  • composio-google provides the Google ADK provider
  • 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 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.")
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
print("Initializing Composio client...")
composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

print("Creating Composio session...")
composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["clickmeeting"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url
print(f"Composio MCP HTTP 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
print("Creating Composio toolset for the agent...")
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )
)

root_agent = Agent(
    model="gemini-2.5-pro",
    name="composio_agent",
    description="An agent that uses Clickmeeting 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 Clickmeeting 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 Clickmeeting 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

def main():
    try:
        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.")

        print("Initializing Composio client...")
        composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

        print("Creating Composio session...")
        composio_session = composio_client.create(
            user_id=COMPOSIO_USER_ID,
            toolkits=["clickmeeting"],
        )

        COMPOSIO_MCP_URL = composio_session.mcp.url
        print(f"Composio MCP HTTP URL: {COMPOSIO_MCP_URL}")

        print("Creating Composio toolset for the agent...")
        composio_toolset = McpToolset(
            connection_params=StreamableHTTPConnectionParams(
                url=COMPOSIO_MCP_URL,
                headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
            )
        )

        root_agent = Agent(
            model="gemini-2.5-pro",
            name="composio_agent",
            description="An agent that uses Clickmeeting 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 Clickmeeting operations."
            ),
            tools=[composio_toolset],
        )

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

    except Exception as e:
        print(f"\nAn error occurred during agent setup: {e}")

if __name__ == "__main__":
    main()

Conclusion

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

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Clickmeeting 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 Clickmeeting MCP Agent with another framework

FAQ

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

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

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

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

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
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.