How to integrate Clickmeeting MCP with LlamaIndex

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Clickmeeting Logo
LlamaIndex Logo
divider

Introduction

This guide walks you through connecting Clickmeeting to LlamaIndex 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 LlamaIndex 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:
  • Set your OpenAI and Composio API keys
  • Install LlamaIndex and Composio packages
  • Create a Composio Tool Router session for Clickmeeting
  • Connect LlamaIndex to the Clickmeeting MCP server
  • Build a Clickmeeting-powered agent using LlamaIndex
  • Interact with Clickmeeting through natural language

What is LlamaIndex?

LlamaIndex is a data framework for building LLM applications. It provides tools for connecting LLMs to external data sources and services through agents and tools.

Key features include:

  • ReAct Agent: Reasoning and acting pattern for tool-using agents
  • MCP Tools: Native support for Model Context Protocol
  • Context Management: Maintain conversation context across interactions
  • Async Support: Built for async/await patterns

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 you begin, make sure you have:
  • Python 3.8/Node 16 or higher installed
  • A Composio account with the API key
  • An OpenAI API key
  • A Clickmeeting account and project
  • Basic familiarity with async Python/Typescript

Getting API Keys for OpenAI, Composio, and Clickmeeting

OpenAI API key (OPENAI_API_KEY)
  • Go to the OpenAI dashboard
  • Create an API key if you don't have one
  • Assign it to OPENAI_API_KEY in .env
Composio API key and user ID
  • Log into the Composio dashboard
  • Copy your API key from Settings
    • Use this as COMPOSIO_API_KEY
  • Pick a stable user identifier (email or ID)
    • Use this as COMPOSIO_USER_ID

Installing dependencies

pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv

Create a new Python project and install the necessary dependencies:

  • composio-llamaindex: Composio's LlamaIndex integration
  • llama-index: Core LlamaIndex framework
  • llama-index-llms-openai: OpenAI LLM integration
  • llama-index-tools-mcp: MCP client for LlamaIndex
  • python-dotenv: Environment variable management

Set environment variables

bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id

Create a .env file in your project root:

These credentials will be used to:

  • Authenticate with OpenAI's GPT-5 model
  • Connect to Composio's Tool Router
  • Identify your Composio user session for Clickmeeting access

Import modules

import asyncio
import os
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

Create a new file called clickmeeting_llamaindex_agent.py and import the required modules:

Key imports:

  • asyncio: For async/await support
  • Composio: Main client for Composio services
  • LlamaIndexProvider: Adapts Composio tools for LlamaIndex
  • ReActAgent: LlamaIndex's reasoning and action agent
  • BasicMCPClient: Connects to MCP endpoints
  • McpToolSpec: Converts MCP tools to LlamaIndex format

Load environment variables and initialize Composio

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

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_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:

This ensures missing credentials cause early, clear errors before the agent attempts to initialise.

Create a Tool Router session and build the agent function

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["clickmeeting"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")

    description = "An agent that uses Composio Tool Router MCP tools to perform Clickmeeting actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Clickmeeting actions.
    """
    return ReActAgent(tools=tools, llm=llm, description=description, system_prompt=system_prompt, verbose=True)

What's happening here:

  • We create a Composio client using your API key and configure it with the LlamaIndex provider
  • We then create a tool router MCP session for your user, specifying the toolkits we want to use (in this case, clickmeeting)
  • The session returns an MCP HTTP endpoint URL that acts as a gateway to all your configured tools
  • LlamaIndex will connect to this endpoint to dynamically discover and use the available Clickmeeting tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.

Create an interactive chat loop

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

What's happening here:

  • We're creating a direct terminal interface to chat with your Clickmeeting database
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are displayed in a clear, readable format

Define the main entry point

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

What's happening here:

  • We're orchestrating the entire application flow
  • The agent gets built with proper error handling
  • Then we kick off the interactive chat loop so you can start talking to Clickmeeting

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Clickmeeting, then start asking questions.

Complete Code

Here's the complete code to get you started with Clickmeeting and LlamaIndex:

import asyncio
import os
import signal
import dotenv

from composio import Composio
from composio_llamaindex import LlamaIndexProvider
from llama_index.core.agent.workflow import ReActAgent
from llama_index.core.workflow import Context
from llama_index.llms.openai import OpenAI
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec

dotenv.load_dotenv()

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

if not OPENAI_API_KEY:
    raise ValueError("OPENAI_API_KEY is not set")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")

async def build_agent() -> ReActAgent:
    composio_client = Composio(
        api_key=COMPOSIO_API_KEY,
        provider=LlamaIndexProvider(),
    )

    session = composio_client.create(
        user_id=COMPOSIO_USER_ID,
        toolkits=["clickmeeting"],
    )

    mcp_url = session.mcp.url
    print(f"Composio MCP URL: {mcp_url}")

    mcp_client = BasicMCPClient(mcp_url, headers={"x-api-key": COMPOSIO_API_KEY})
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    llm = OpenAI(model="gpt-5")
    description = "An agent that uses Composio Tool Router MCP tools to perform Clickmeeting actions."
    system_prompt = """
    You are a helpful assistant connected to Composio Tool Router.
    Use the available tools to answer user queries and perform Clickmeeting actions.
    """
    return ReActAgent(
        tools=tools,
        llm=llm,
        description=description,
        system_prompt=system_prompt,
        verbose=True,
    );

async def chat_loop(agent: ReActAgent) -> None:
    ctx = Context(agent)
    print("Type 'quit', 'exit', or Ctrl+C to stop.")

    while True:
        try:
            user_input = input("\nYou: ").strip()
        except (KeyboardInterrupt, EOFError):
            print("\nBye!")
            break

        if not user_input or user_input.lower() in {"quit", "exit"}:
            print("Bye!")
            break

        try:
            print("Agent: ", end="", flush=True)
            handler = agent.run(user_input, ctx=ctx)

            async for event in handler.stream_events():
                # Stream token-by-token from LLM responses
                if hasattr(event, "delta") and event.delta:
                    print(event.delta, end="", flush=True)
                # Show tool calls as they happen
                elif hasattr(event, "tool_name"):
                    print(f"\n[Using tool: {event.tool_name}]", flush=True)

            # Get final response
            response = await handler
            print()  # Newline after streaming
        except KeyboardInterrupt:
            print("\n[Interrupted]")
            continue
        except Exception as e:
            print(f"\nError: {e}")

async def main() -> None:
    agent = await build_agent()
    await chat_loop(agent)

if __name__ == "__main__":
    # Handle Ctrl+C gracefully
    signal.signal(signal.SIGINT, lambda s, f: (print("\nBye!"), exit(0)))
    try:
        asyncio.run(main())
    except KeyboardInterrupt:
        print("\nBye!")

Conclusion

You've successfully connected Clickmeeting to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Clickmeeting tools through an MCP endpoint
  • LlamaIndex's ReActAgent handles reasoning and orchestration; Composio handles integrations
  • The agent becomes more capable without increasing prompt size
  • Async Python provides clean, efficient execution of agent workflows
You can easily extend this to other toolkits like Gmail, Notion, Stripe, GitHub, and more by adding them to the toolkits parameter.

How to build Clickmeeting MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Clickmeeting MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Clickmeeting MCP with Claude Agent SDK

Google ADK

Google ADK

Use Clickmeeting MCP with Google ADK

LangChain

LangChain

Use Clickmeeting MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Clickmeeting MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Clickmeeting MCP with Mastra AI

CrewAI

CrewAI

Use Clickmeeting MCP with CrewAI

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 LlamaIndex?

Yes, you can. LlamaIndex 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.

Book a call↗Get started for free