# How to integrate Zoom MCP with LlamaIndex ```json { "title": "How to integrate Zoom MCP with LlamaIndex", "toolkit": "Zoom", "toolkit_slug": "zoom", "framework": "LlamaIndex", "framework_slug": "llama-index", "url": "https://composio.dev/toolkits/zoom/framework/llama-index", "markdown_url": "https://composio.dev/toolkits/zoom/framework/llama-index.md", "updated_at": "2026-05-06T08:35:09.616Z" } ``` ## Introduction This guide walks you through connecting Zoom to LlamaIndex using the Composio tool router. By the end, you'll have a working Zoom agent that can schedule a zoom meeting for tomorrow, add a registrant to your next webinar, summarize your last recorded meeting through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Zoom account through Composio's Zoom MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved. ## Also integrate Zoom with - [ChatGPT](https://composio.dev/toolkits/zoom/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/zoom/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/zoom/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/zoom/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/zoom/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/zoom/framework/codex) - [Cursor](https://composio.dev/toolkits/zoom/framework/cursor) - [VS Code](https://composio.dev/toolkits/zoom/framework/vscode) - [OpenCode](https://composio.dev/toolkits/zoom/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/zoom/framework/openclaw) - [Hermes](https://composio.dev/toolkits/zoom/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/zoom/framework/cli) - [Google ADK](https://composio.dev/toolkits/zoom/framework/google-adk) - [LangChain](https://composio.dev/toolkits/zoom/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/zoom/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/zoom/framework/mastra-ai) - [CrewAI](https://composio.dev/toolkits/zoom/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 Zoom - Connect LlamaIndex to the Zoom MCP server - Build a Zoom-powered agent using LlamaIndex - Interact with Zoom 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 Zoom MCP server, and what's possible with it? The Zoom MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Zoom account. It provides structured and secure access to your meetings, webinars, and usage data, so your agent can schedule meetings, register attendees, retrieve recordings, summarize sessions, and analyze participant engagement on your behalf. - Automated meeting scheduling and management: Instruct your agent to create new Zoom meetings, fetch details for upcoming or past meetings, and manage all your session logistics effortlessly. - Seamless participant and registrant registration: Have your agent add attendees or registrants to meetings and webinars, handling all required information and permissions automatically. - On-demand access to recordings and summaries: Let your agent retrieve meeting recordings or generate AI-powered meeting summaries, making it easy to review or share past sessions. - Insightful participant analytics: Ask your agent to fetch detailed lists of past meeting participants or generate daily usage reports, helping you track engagement and attendance trends. - Efficient recording and data cleanup: Direct your agent to delete outdated recordings or manage your Zoom storage, keeping your account streamlined and organized. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `ZOOM_ADD_A_MEETING_REGISTRANT` | Add a meeting registrant | This text guides on creating and customizing a user's registration for a zoom meeting, with a max of 4,999 registrants. preconditions include the host being licensed. api scopes and a light rate limit apply. | | `ZOOM_ADD_A_WEBINAR_REGISTRANT` | Add a webinar registrant | Zoom users with a webinar plan can create and manage webinars, broadcasting to up to 10,000 attendees. registration requires a pro plan, specific permissions, and is governed by a "light" rate limit. | | `ZOOM_CREATE_A_MEETING` | Create a meeting | Enable zoom meeting creation via user-level apps with "me". "start url" for hosts expires in 2 hours, or 90 days for "custcreate" users. renew via api, capped at 100 requests/day. requires "meeting:write" permission, subject to medium rate limit. | | `ZOOM_DELETE_MEETING_RECORDINGS` | Delete meeting recordings | Summary: to delete all meeting recordings, ensure the user's account has cloud recording enabled. required permissions include `recording:write:admin` and `recording:write` with a `light` rate limit label. | | `ZOOM_GET_A_MEETING` | Get a meeting | The text provides details on api permissions for reading meeting information, categorizing permissions into general and granular scopes, and labels the rate limit as 'light'. | | `ZOOM_GET_A_MEETING_SUMMARY` | Get a meeting summary | Meeting summary info requires a pro+ host plan, ai companion enabled, excluding e2ee meetings. scopes include meeting summary:read and admin versions. rate limit: light. | | `ZOOM_GET_A_WEBINAR` | Get a webinar | Access zoom webinar details requires pro or higher plan and webinar add-on. scopes include `webinar:read:admin` and `webinar:read`. granular scopes and a 'light' rate limit also apply. | | `ZOOM_GET_DAILY_USAGE_REPORT` | Get daily usage report | The daily report provides zoom service usage details, like new users, meetings, participants, and minutes per day for a month, requiring a pro plan or higher. it has a 'heavy' rate limit. | | `ZOOM_GET_MEETING_RECORDINGS` | Get meeting recordings | To download meeting recordings, use `download url`. include oauth token in the header for passcode-protected ones. supports `recording:read` and `phone recording:read:admin` scopes, with a `light` rate limit. | | `ZOOM_GET_PAST_MEETING_PARTICIPANTS` | Get past meeting participants | Api allows paid users (pro+) to fetch past meeting attendee info, excluding solo participants. requires double encoding for certain uuids, with `meeting:read` scope and others. rate limit is medium. | | `ZOOM_LIST_ALL_RECORDINGS` | List all recordings | This text details how to list zoom cloud recordings for a user, notably by using "me" for user-level apps and requiring an oauth token for access. it requires a pro plan, cloud recording enabled, and has a medium rate limit. | | `ZOOM_LIST_ARCHIVED_FILES` | List archived files | Zoom's archiving solution enables administrators to automatically record and archive meeting data to third-party platforms for compliance, needing the meeting and webinar archiving feature enabled. | | `ZOOM_LIST_DEVICES` | List devices | This api lets you list devices. **scopes:** `device:read:admin`,`device:write:admin` **[rate limit label](https://marketplace.zoom.us/docs/api-reference/rate-limits#rate-limits):** `heavy` | | `ZOOM_LIST_MEETINGS` | List meetings | This zoom api lists a user's scheduled meetings using the `me` value for user-level apps, excluding instant meetings and only showing unexpired ones. it requires specific scopes and has a `medium` rate limit. | | `ZOOM_LIST_WEBINAR_PARTICIPANTS` | List webinar participants | Get a list of past webinar participants with a pro plan or above plus an add-on. requires specific scopes and has a medium rate limit. | | `ZOOM_LIST_WEBINARS` | List webinars | The api lists all scheduled webinars for zoom users with a webinar plan, using `me` for user-level apps. it only shows unexpired webinars for hosts broadcasting to up to 10,000 attendees. requires pro plan upwards and specific scopes. rate limit: medium. | | `ZOOM_UPDATE_A_MEETING` | Update a meeting | To update a meeting via api, ensure `start time` is future-dated; `recurrence` is needed. limit: 100 requests/day, 100 updates/meeting in 24 hrs. requires `meeting:write` and `meeting:write:admin` scopes, with a `light` rate limit. | ## Supported Triggers | Trigger slug | Name | Description | |---|---|---| | `ZOOM_DAILY_USAGE_REPORT_CHANGED_TRIGGER` | Daily Usage Report Changed | Triggers when the Zoom daily usage report changes for a selected year/month. This trigger monitors daily usage statistics including: - New users added - Number of meetings held - Participant counts - Meeting minutes consumed | | `ZOOM_MEETING_DETAILS_CHANGED_TRIGGER` | Meeting Details Changed | Triggers when a specific meeting's details change. Detects changes such as: - Meeting topic changes - Agenda updates - Schedule changes (timezone, duration) - Settings modifications (waiting room, recording, video, etc.) - Password changes - Recurrence pattern updates | | `ZOOM_MEETING_RECORDING_CHANGED_TRIGGER` | Meeting Recording Changed | Triggers when a specific meeting's cloud recordings change. Detects changes such as: - New recording files appearing - Recording processing completion (status changes) - Recording metadata changes (count, size, etc.) - New participant audio files | | `ZOOM_MEETING_SUMMARY_UPDATED_TRIGGER` | Meeting Summary Created or Updated | Triggers when a meeting summary is created or updated for a specific meeting. IMPORTANT: This trigger requires a PAID Zoom account (Pro, Business, or Enterprise plan). Free Zoom accounts cannot use this feature. Additionally requires: - AI Companion feature enabled in account settings - Meeting must not be end-to-end encrypted (E2EE) - Meeting summary must be enabled and generated for the meeting | | `ZOOM_NEW_CLOUD_RECORDING_TRIGGER` | New Cloud Recording | Triggers when a new cloud recording meeting instance appears for a user. | | `ZOOM_NEW_MEETING_CREATED_TRIGGER` | New Meeting Created | Triggers when a new Zoom meeting is created for a user. | | `ZOOM_NEW_MEETING_PARTICIPANT_TRIGGER` | New Meeting Participant | Triggers when a new participant appears in a past meeting's participant report. | | `ZOOM_NEW_WEBINAR_CREATED_TRIGGER` | New Webinar Created | Triggers when a new webinar is created for a user. | | `ZOOM_NEW_WEBINAR_PARTICIPANT_TRIGGER` | New Webinar Participant | Triggers when a new participant appears in a past webinar's participant list. | | `ZOOM_USER_INFORMATION_CHANGED_TRIGGER` | User Information Changed | Triggers when a Zoom user's information changes. Detects changes such as: - Profile information updates (name, email, display name) - Role or type changes - Department, job title, or location updates - Contact information changes (phone, timezone) - Status changes (active, inactive, pending) - Settings updates (language, pronouns, etc.) | | `ZOOM_WEBINAR_DETAILS_CHANGED_TRIGGER` | Webinar Details Changed | Triggers when a Zoom webinar's details change. Detects changes such as: - Topic updates - Start time changes - Agenda modifications - Duration changes - Settings updates (host video, registration type, audio options, etc.) - Status changes - Occurrence updates for recurring webinars - Recurrence pattern changes | ## Creating MCP Server - Stand-alone vs Composio SDK The Zoom MCP server is an implementation of the Model Context Protocol that connects your AI agent to Zoom. It provides structured and secure access so your agent can perform Zoom 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 Zoom account and project - Basic familiarity with async Python/Typescript ### 1. Getting API Keys for OpenAI, Composio, and Zoom 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 Zoom 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, zoom) - 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 Zoom 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=["zoom"], ) 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 Zoom actions." system_prompt = """ You are a helpful assistant connected to Composio Tool Router. Use the available tools to answer user queries and perform Zoom 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: ["zoom"], }, ); 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 Zoom 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) { 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 Zoom ```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 Zoom, 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=["zoom"], ) 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 Zoom actions." system_prompt = """ You are a helpful assistant connected to Composio Tool Router. Use the available tools to answer user queries and perform Zoom 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: ["zoom"], }, ); 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 Zoom actions." , llm, tools, }); return agent; } async function chatLoop(agent: ReturnType) { 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 Zoom to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways: - Tool Router dynamically exposes Zoom 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 Zoom MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/zoom/framework/chatgpt) - [OpenAI Agents SDK](https://composio.dev/toolkits/zoom/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/zoom/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/zoom/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/zoom/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/zoom/framework/codex) - [Cursor](https://composio.dev/toolkits/zoom/framework/cursor) - [VS Code](https://composio.dev/toolkits/zoom/framework/vscode) - [OpenCode](https://composio.dev/toolkits/zoom/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/zoom/framework/openclaw) - [Hermes](https://composio.dev/toolkits/zoom/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/zoom/framework/cli) - [Google ADK](https://composio.dev/toolkits/zoom/framework/google-adk) - [LangChain](https://composio.dev/toolkits/zoom/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/zoom/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/zoom/framework/mastra-ai) - [CrewAI](https://composio.dev/toolkits/zoom/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. - [Clickmeeting](https://composio.dev/toolkits/clickmeeting) - ClickMeeting is a cloud-based platform for running online meetings and webinars. It helps businesses and individuals host, manage, and engage virtual audiences with ease. - [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. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Zoom MCP? With a standalone Zoom MCP server, the agents and LLMs can only access a fixed set of Zoom tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Zoom 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 Zoom tools. ### Can I manage the permissions and scopes for Zoom while using Tool Router? Yes, absolutely. You can configure which Zoom 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 Zoom data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)