# How to integrate Clickmeeting MCP with LlamaIndex

```json
{
  "title": "How to integrate Clickmeeting MCP with LlamaIndex",
  "toolkit": "Clickmeeting",
  "toolkit_slug": "clickmeeting",
  "framework": "LlamaIndex",
  "framework_slug": "llama-index",
  "url": "https://composio.dev/toolkits/clickmeeting/framework/llama-index",
  "markdown_url": "https://composio.dev/toolkits/clickmeeting/framework/llama-index.md",
  "updated_at": "2026-05-12T10:06:26.281Z"
}
```

## 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 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.

## Also integrate Clickmeeting with

- [OpenAI Agents SDK](https://composio.dev/toolkits/clickmeeting/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/clickmeeting/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/clickmeeting/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/clickmeeting/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/clickmeeting/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/clickmeeting/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/clickmeeting/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/clickmeeting/framework/cli)
- [Google ADK](https://composio.dev/toolkits/clickmeeting/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/clickmeeting/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/clickmeeting/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/clickmeeting/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/clickmeeting/framework/crew-ai)

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

| Tool slug | Name | Description |
|---|---|---|
| `CLICKMEETING_CREATE_ACCESS_TOKENS` | Create Access Tokens | Tool to generate access tokens for conference participants. Use when room access_type=3 (token protected) and you need unique tokens for attendees. |
| `CLICKMEETING_CREATE_CONFERENCE` | Create Conference | Tool to create a new conference. Use when you need to schedule or start a meeting/webinar after authentication. |
| `CLICKMEETING_CREATE_CONTACT` | Create Contact | Tool to create a new contact in your ClickMeeting account. Use when you need to add or pre-register an attendee before scheduling an event. |
| `CLICKMEETING_DELETE_CONFERENCE` | Delete Conference | Tool to delete a specific conference. Use after confirming the conference is no longer needed. |
| `CLICKMEETING_DELETE_FILE` | Delete File | Permanently delete a file from the ClickMeeting file library. Use this action to remove unwanted or outdated files (presentations, images, videos, etc.) from your library. Before calling this action, use Get File Library to find the file_id. WARNING: Deletion is irreversible - the file cannot be recovered once deleted. |
| `CLICKMEETING_DELETE_RECORDING` | Delete Recording | Permanently delete a specific recording from a conference room. Use this action to remove an unwanted or outdated recording. Before calling this action: 1. Use Get Conferences to find the conference_id 2. Use Get Recordings to find the recording_id within that conference WARNING: Deletion is irreversible. The recording file cannot be recovered once deleted. |
| `CLICKMEETING_DELETE_RECORDINGS` | Delete Recordings | Tool to delete all recordings for a conference room. Use when you need to clear all saved recordings for a specific conference before archiving or reusing it. |
| `CLICKMEETING_DOWNLOAD_FILE` | Download File | Download the content of a specific file from the ClickMeeting file library. Use when you need to retrieve the actual file content for processing or storage. |
| `CLICKMEETING_GENERATE_AUTOLOGIN_URL` | Generate Autologin Hash | Generate an autologin hash for a conference participant. This tool creates a hash that allows direct access to a ClickMeeting conference room without requiring separate login. Use it to build auto-login URLs in the format: ?l= The returned hash is time-sensitive and tied to the specific participant details provided. |
| `CLICKMEETING_GENERATE_SESSION_PDF_REPORT` | Generate Session PDF Report | Generates a PDF report containing analytics and details for a specific conference session. The report includes session attendance, duration, and other metrics. Use this when you need to export session data as a downloadable PDF document. Note: This action requires a valid session_id. Sessions are only created after a conference has been held (started and ended). Use get_conference_sessions to find available sessions. The PDF generation may be asynchronous - check the 'status' field in the response. If status is 'NEW' or 'IN_PROGRESS', poll again until status becomes 'FINISHED'. |
| `CLICKMEETING_GET_CHAT_DETAILS` | Get Chat Details | Tool to retrieve details of a specific chat session. Use when you have the chat_id and need its metadata and messages. |
| `CLICKMEETING_GET_CHATS` | Get Chats | Tool to retrieve a list of all chat sessions. Use when you need to list available chats in your account. |
| `CLICKMEETING_GET_CONFERENCE_DETAILS` | Get Conference Details | Retrieve detailed information about a specific ClickMeeting conference room. Returns comprehensive data including room URL, access settings, phone dial-in PINs, timezone, status, and configuration options. Use the meeting_id from Get Conferences action or from a previously created conference. |
| `CLICKMEETING_GET_CONFERENCE_FILES` | Get Conference Files | Retrieves the list of files uploaded to a specific conference room's file library. Returns file metadata including download URLs, conversion status, and thumbnails. Files must be uploaded via the upload_file action before they appear here. Returns an empty list if no files exist or if the conference ID is invalid. |
| `CLICKMEETING_GET_CONFERENCES` | Get Conferences | Retrieve a list of conference rooms from your ClickMeeting account filtered by status. Use 'active' to get current/upcoming meetings, or 'inactive' to get archived/ended meetings. Returns details including room URLs, access settings, schedules, and registration info. |
| `CLICKMEETING_GET_CONFERENCE_SESSIONS` | Get Conference Sessions | Retrieves past sessions for a conference room. Sessions are only created when a conference is actually held (participants join). Use this to get historical data like session times and attendance counts after meetings have occurred. Returns an empty list if the conference has never been held. |
| `CLICKMEETING_GET_CONFERENCE_SKINS` | Get Conference Skins | Retrieves a list of available conference room skins that can be used to customize the appearance of webinar/meeting rooms. Each skin includes an ID (for use when creating/updating conferences), a display name, and a preview thumbnail URL. Note: This feature may require a paid ClickMeeting plan with custom branding access. |
| `CLICKMEETING_GET_FILE_DETAILS` | Get File Details | Retrieve detailed information about a specific file from the ClickMeeting file library. Returns file status, URL, document type, conversion progress, and upload date. Use this to check file availability and status before using in conferences. |
| `CLICKMEETING_GET_FILE_LIBRARY` | Get File Library | Retrieve a list of files from the ClickMeeting file library. Returns all uploaded files (presentations, images, videos, audio) available for use in meetings. Use this to browse, search, or inventory files before assigning them to conferences. |
| `CLICKMEETING_GET_PHONE_GATEWAYS` | Get Phone Gateways | Retrieve available phone dial-in numbers for ClickMeeting webinars. Returns a list of worldwide phone gateways that participants can call to join a webinar via audio conference. Each gateway includes the country code, city location, dial-in number, and geographic coordinates. No parameters are required. Use this tool when you need to provide dial-in options for webinar participants who prefer to join by phone, or to display available dial-in numbers in meeting invitations. |
| `CLICKMEETING_GET_PING` | Ping API | Tool to check API service status. Use when verifying the ClickMeeting API connection before making requests. |
| `CLICKMEETING_GET_REGISTRATIONS` | Get Registrations | Tool to retrieve registrations for a conference room by status. Use after obtaining the conference_id to fetch registrations filtered by state. |
| `CLICKMEETING_GET_SESSION_ATTENDEES` | Get Session Attendees | Retrieves the list of attendees who participated in a specific session of a conference room. Returns attendee details including device info, role, rating, and poll responses. Sessions are created when a conference is started, so this action only returns data for conferences that have been held. Use Get Conference Sessions to find valid session IDs. |
| `CLICKMEETING_GET_SESSION_DETAILS` | Get Session Details | Retrieve detailed statistics for a specific past conference session. Returns attendance data (total and max concurrent visitors), participant list with join/leave times, and PDF report generation URLs. Sessions are only available after a conference has actually been held - scheduled or active conferences without any past meetings will not have sessions. First use Get Conference Sessions to obtain valid session_id values. |
| `CLICKMEETING_GET_SESSION_POLL_DETAILS` | Get Session Poll Details | Tool to retrieve details of a specific poll conducted during a session. Use after confirming conference_id, session_id, and poll_id to analyze poll results. |
| `CLICKMEETING_GET_SESSION_QA_HISTORY` | Get Session Q&A History | Tool to retrieve the Q&A history for a specific session. Use after confirming session_id to list all questions and answers asked during the session. NOTE: The session must have Q&A data available; sessions without Q&A will return an empty list or 404. |
| `CLICKMEETING_GET_SESSION_RECORDINGS` | Get Session Recordings | Retrieve all recordings for a conference room. Each recording includes the duration, file size, start time, and a download URL (expires after 5 minutes). Use after confirming the room_id from the Get Conferences action. Note: Recordings are only available after a conference session has been held and recorded. |
| `CLICKMEETING_GET_SESSION_REGISTRATIONS` | Get Session Registrations | Retrieve registrations for a specific session within a conference room. Requires both conference_id (room ID) and session_id. Use CLICKMEETING_GET_CONFERENCES to get conference IDs and CLICKMEETING_GET_CONFERENCE_SESSIONS to get session IDs. |
| `CLICKMEETING_GET_SESSION_SURVEY_DETAILS` | Get Session Survey Details | Tool to retrieve details of a specific survey/poll conducted during a session. Use after obtaining conference_id, session_id, and survey_id from their respective actions. Note: ClickMeeting provides poll/survey data through the session attendees endpoint. |
| `CLICKMEETING_GET_SESSION_SURVEYS` | Get Session Surveys | Retrieves the list of surveys conducted during a specific conference session. Sessions are created when a conference is started, so this action only returns data for conferences that have been held. Use Get Conference Sessions to find valid session IDs first. Returns an empty list if no surveys exist for the session. |
| `CLICKMEETING_GET_TIME_ZONE_LIST` | Get Time Zone List | Retrieves all available time zones supported by ClickMeeting. Returns IANA time zone names (e.g., 'Europe/Warsaw', 'America/New_York'). Use this to get valid time zone values when creating or scheduling conferences. |
| `CLICKMEETING_GET_TIME_ZONE_LIST_BY_COUNTRY` | Get Time Zone List by Country | Retrieve available time zones for a specific country by ISO 3166-1 alpha-2 country code. Returns a list of IANA time zone identifiers (e.g., 'America/New_York', 'Europe/Warsaw'). Useful when scheduling conferences and needing to present time zone options relevant to a specific country. Example: 'Get time zones for country_code=US' returns US time zones like America/New_York, America/Los_Angeles, etc. |
| `CLICKMEETING_GET_TOKEN_BY_EMAIL` | Get Token By Email | Tool to retrieve access tokens assigned to a specific email address for a token-protected conference room. Use this action when you need to get tokens for participants in rooms with access_type=3 (token-based access). |
| `CLICKMEETING_LIST_ACCESS_TOKENS` | List Access Tokens | Tool to retrieve all generated access tokens for a token-protected conference room. Use when you need to view token values, associated emails, and first use dates for access control. Only works with conferences that have access_type=3 (token-based protection). |
| `CLICKMEETING_LIST_REGISTRATIONS_BY_STATUS` | List Registrations By Status | Tool to retrieve registered participants of a conference room filtered by registration status. Use when you need to get all registrations or only active registrations for a specific conference. |
| `CLICKMEETING_REGISTER_PARTICIPANT` | Register Participant | Tool to register a participant for a conference room. Use after obtaining a valid room ID. |
| `CLICKMEETING_SEND_INVITATION` | Send Invitation | Tool to send invitation emails to participants for a ClickMeeting conference. Use this after creating a conference to invite attendees by email. Supports multiple recipients, different templates, and role assignment. |
| `CLICKMEETING_UPDATE_CONFERENCE` | Update Conference | Tool to update an existing conference room's parameters. Use when you need to modify conference settings such as name, type, access mode, lobby, schedule, or registration. |
| `CLICKMEETING_UPLOAD_FILE` | Upload File | Upload a file to the ClickMeeting file library. Files can be uploaded to the user's general library or to a specific conference room. Uploaded files are available for use in meetings as presentations, videos, or other materials. |

## Supported Triggers

None listed.

## Creating MCP Server - Stand-alone vs Composio SDK

The Clickmeeting MCP server is an implementation of the Model Context Protocol that connects your AI agent to Clickmeeting. It provides structured and secure access so your agent can perform Clickmeeting operations on your behalf through a secure, permission-based interface.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. 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

### 1. Getting API Keys for OpenAI, Composio, and Clickmeeting

No description provided.

### 2. Installing dependencies

No description provided.
```python
pip install composio-llamaindex llama-index llama-index-llms-openai llama-index-tools-mcp python-dotenv
```

```typescript
npm install @composio/llamaindex @llamaindex/openai @llamaindex/tools @llamaindex/workflow dotenv
```

### 3. Set environment variables

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
```bash
OPENAI_API_KEY=your-openai-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id
```

### 4. Import modules

No description provided.
```python
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()
```

```typescript
import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();
```

### 5. Load environment variables and initialize Composio

No description provided.
```python
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")
```

```typescript
const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) throw new Error("OPENAI_API_KEY is not set");
if (!COMPOSIO_API_KEY) throw new Error("COMPOSIO_API_KEY is not set");
if (!COMPOSIO_USER_ID) throw new Error("COMPOSIO_USER_ID is not set");
```

### 6. Create a Tool Router session and build the agent function

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.
```python
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)
```

```typescript
async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["clickmeeting"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
        description : "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Clickmeeting actions." ,
    llm,
    tools,
  });

  return agent;
}
```

### 7. Create an interactive chat loop

No description provided.
```python
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}")
```

```typescript
async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}
```

### 8. Define the main entry point

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
```python
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!")
```

```typescript
async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err) {
    console.error("Failed to start agent:", err);
    process.exit(1);
  }
}

main();
```

### 9. Run the agent

When prompted, authenticate and authorise your agent with Clickmeeting, then start asking questions.
```bash
python llamaindex_agent.py
```

```typescript
npx ts-node llamaindex-agent.ts
```

## Complete Code

```python
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!")
```

```typescript
import "dotenv/config";
import readline from "node:readline/promises";
import { stdin as input, stdout as output } from "node:process";

import { Composio } from "@composio/core";
import { LlamaindexProvider } from "@composio/llamaindex";

import { mcp } from "@llamaindex/tools";
import { agent as createAgent } from "@llamaindex/workflow";
import { openai } from "@llamaindex/openai";

dotenv.config();

const OPENAI_API_KEY = process.env.OPENAI_API_KEY;
const COMPOSIO_API_KEY = process.env.COMPOSIO_API_KEY;
const COMPOSIO_USER_ID = process.env.COMPOSIO_USER_ID;

if (!OPENAI_API_KEY) {
    throw new Error("OPENAI_API_KEY is not set in the environment");
  }
if (!COMPOSIO_API_KEY) {
    throw new Error("COMPOSIO_API_KEY is not set in the environment");
  }
if (!COMPOSIO_USER_ID) {
    throw new Error("COMPOSIO_USER_ID is not set in the environment");
  }

async function buildAgent() {

  console.log(`Initializing Composio client...${COMPOSIO_USER_ID!}...`);
  console.log(`COMPOSIO_USER_ID: ${COMPOSIO_USER_ID!}...`);

  const composio = new Composio({
    apiKey: COMPOSIO_API_KEY,
    provider: new LlamaindexProvider(),
  });

  const session = await composio.create(
    COMPOSIO_USER_ID!,
    {
      toolkits: ["clickmeeting"],
    },
  );

  const mcpUrl = session.mcp.url;
  console.log(`Composio Tool Router MCP URL: ${mcpUrl}`);

  const server = mcp({
    url: mcpUrl,
    clientName: "composio_tool_router_with_llamaindex",
    requestInit: {
      headers: {
        "x-api-key": COMPOSIO_API_KEY!,
      },
    },
    // verbose: true,
  });

  const tools = await server.tools();

  const llm = openai({ apiKey: OPENAI_API_KEY, model: "gpt-5" });

  const agent = createAgent({
    name: "composio_tool_router_with_llamaindex",
    description:
      "An agent that uses Composio Tool Router MCP tools to perform actions.",
    systemPrompt:
      "You are a helpful assistant connected to Composio Tool Router."+
"Use the available tools to answer user queries and perform Clickmeeting actions." ,
    llm,
    tools,
  });

  return agent;
}

async function chatLoop(agent: ReturnType<typeof createAgent>) {
  const rl = readline.createInterface({ input, output });

  console.log("Type 'quit' or 'exit' to stop.");

  while (true) {
    let userInput: string;

    try {
      userInput = (await rl.question("\nYou: ")).trim();
    } catch {
      console.log("\nAgent: Bye!");
      break;
    }

    if (!userInput) {
      continue;
    }

    const lower = userInput.toLowerCase();
    if (lower === "quit" || lower === "exit") {
      console.log("Agent: Bye!");
      break;
    }

    try {
      process.stdout.write("Agent: ");

      const stream = agent.runStream(userInput);
      let finalResult: any = null;

      for await (const event of stream) {
        // The event.data contains the streamed content
        const data: any = event.data;

        // Check for streaming delta content
        if (data?.delta) {
          process.stdout.write(data.delta);
        }

        // Store final result for fallback
        if (data?.result || data?.message) {
          finalResult = data;
        }
      }

      // If no streaming happened, show the final result
      if (finalResult) {
        const answer =
          finalResult.result ??
          finalResult.message?.content ??
          finalResult.message ??
          "";
        if (answer && typeof answer === "string" && !answer.includes("[object")) {
          process.stdout.write(answer);
        }
      }

      console.log(); // New line after streaming completes
    } catch (err: any) {
      console.error("\nAgent error:", err?.message ?? err);
    }
  }

  rl.close();
}

async function main() {
  try {
    const agent = await buildAgent();
    await chatLoop(agent);
  } catch (err: any) {
    console.error("Failed to start agent:", err?.message ?? err);
    process.exit(1);
  }
}

main();
```

## 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](https://composio.dev/toolkits/clickmeeting/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/clickmeeting/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/clickmeeting/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/clickmeeting/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/clickmeeting/framework/codex)
- [OpenClaw](https://composio.dev/toolkits/clickmeeting/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/clickmeeting/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/clickmeeting/framework/cli)
- [Google ADK](https://composio.dev/toolkits/clickmeeting/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/clickmeeting/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/clickmeeting/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/clickmeeting/framework/mastra-ai)
- [CrewAI](https://composio.dev/toolkits/clickmeeting/framework/crew-ai)

## Related Toolkits

- [Gmail](https://composio.dev/toolkits/gmail) - Gmail is Google's email service with powerful spam protection, search, and G Suite integration. It keeps your inbox organized and makes communication fast and reliable.
- [Outlook](https://composio.dev/toolkits/outlook) - Outlook is Microsoft's email and calendaring platform for unified communications and scheduling. It helps users stay organized with powerful email, contacts, and calendar management.
- [Slack](https://composio.dev/toolkits/slack) - Slack is a channel-based messaging platform for teams and organizations. It helps people collaborate in real time, share files, and connect all their tools in one place.
- [Gong](https://composio.dev/toolkits/gong) - Gong is a platform for video meetings, call recording, and team collaboration. It helps teams capture conversations, analyze calls, and turn insights into action.
- [Microsoft teams](https://composio.dev/toolkits/microsoft_teams) - Microsoft Teams is a collaboration platform that combines chat, meetings, and file sharing within Microsoft 365. It keeps distributed teams connected and productive through seamless virtual communication.
- [Slackbot](https://composio.dev/toolkits/slackbot) - Slackbot is a conversational automation tool for Slack that handles reminders, notifications, and automated responses. It boosts team productivity by streamlining onboarding, answering FAQs, and managing timely alerts—all right inside Slack.
- [2chat](https://composio.dev/toolkits/_2chat) - 2chat is an API platform for WhatsApp and multichannel text messaging. It streamlines chat automation, group management, and real-time messaging for developers.
- [Agent mail](https://composio.dev/toolkits/agent_mail) - Agent mail provides AI agents with dedicated email inboxes for sending, receiving, and managing emails. It empowers agents to communicate autonomously with people, services, and other agents—no human intervention needed.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Chatwork](https://composio.dev/toolkits/chatwork) - Chatwork is a team communication platform with group chats, file sharing, and task management. It helps businesses boost collaboration and streamline productivity.
- [Confluence](https://composio.dev/toolkits/confluence) - Confluence is Atlassian's team collaboration and knowledge management platform. It helps your team organize, share, and update documents and project content in one secure workspace.
- [Dailybot](https://composio.dev/toolkits/dailybot) - DailyBot streamlines team collaboration with chat-based standups, reminders, and polls. It keeps work flowing smoothly in your favorite messaging platforms.
- [Dialmycalls](https://composio.dev/toolkits/dialmycalls) - Dialmycalls is a mass notification service for sending voice and text messages to contacts. It helps teams and organizations quickly broadcast urgent alerts and updates.
- [Dialpad](https://composio.dev/toolkits/dialpad) - Dialpad is a cloud-based business phone and contact center system for teams. It unifies voice, video, messaging, and meetings across your devices.
- [Discord](https://composio.dev/toolkits/discord) - Discord is a real-time messaging and VoIP platform for communities and teams. It lets users chat, share media, and collaborate across public and private channels.
- [Discordbot](https://composio.dev/toolkits/discordbot) - Discordbot is an automation tool for Discord servers that handles moderation, messaging, and user engagement. It helps communities run smoothly by automating routine and complex tasks.
- [Echtpost](https://composio.dev/toolkits/echtpost) - Echtpost is a secure digital communication platform for encrypted document and message exchange. It ensures confidential data stays private and protected during transmission.
- [Egnyte](https://composio.dev/toolkits/egnyte) - Egnyte is a cloud-based platform for secure file sharing, storage, and governance. It helps teams collaborate efficiently while maintaining data compliance and security.
- [Google Meet](https://composio.dev/toolkits/googlemeet) - Google Meet is a secure video conferencing platform for virtual meetings, chat, and screen sharing. It helps teams connect, collaborate, and communicate seamlessly from anywhere.
- [Heartbeat](https://composio.dev/toolkits/heartbeat) - Heartbeat is a plug-and-play platform for building and managing online communities. It helps you organize users, channels, events, and discussions in one place.

## Frequently Asked Questions

### 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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)