How to integrate Zoom Team Chat MCP with LlamaIndex

This guide walks you through connecting Zoom Team Chat to LlamaIndex using the Composio tool router. By the end, you'll have a working Zoom Team Chat agent that can create channels, manage shared spaces, add space members, bookmark messages, and set reminders through natural language commands. This guide will help you understand how to give your LlamaIndex agent real control over a Zoom Team Chat account through Composio's Zoom Team Chat MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Zoom Team Chat logoZoom Team Chat
Oauth2

Zoom Team Chat is Zoom's persistent messaging service for channels, direct messages, threads, reactions, files, reminders, and shared spaces. It keeps team conversations organized and searchable inside the Zoom workspace.

44 Tools

Introduction

This guide walks you through connecting Zoom Team Chat to LlamaIndex using the Composio tool router. By the end, you'll have a working Zoom Team Chat agent that can create channels, manage shared spaces, add space members, bookmark messages, and set reminders through natural language commands.

This guide will help you understand how to give your LlamaIndex agent real control over a Zoom Team Chat account through Composio's Zoom Team Chat MCP server.

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

Also integrate Zoom Team Chat with

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 Team Chat
  • Connect LlamaIndex to the Zoom Team Chat MCP server
  • Build a Zoom Team Chat-powered agent using LlamaIndex
  • Interact with Zoom Team Chat 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 Team Chat MCP server, and what's possible with it?

The Zoom Team Chat 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 Team Chat account. It provides structured and secure access to your messages, channels, contacts, reminders, and shared spaces, so your agent can send messages, manage channels, organize conversations, set reminders, and coordinate shared spaces on your behalf.

  • Messaging and thread management: Have your agent send messages to channels or contacts, schedule messages, retrieve conversations and threads, and delete messages you no longer need.
  • Channel coordination: Let the agent create, find, join, archive, or delete channels, invite members, and review channel membership.
  • Message organization: Direct your agent to pin, bookmark, react to, or mark messages as read or unread, then review pinned and bookmarked content.
  • Reminders and follow-ups: Instruct your agent to create message reminders, list upcoming reminders, or remove reminders after tasks are complete.
  • Contacts and shared spaces: Have your agent find company contacts, create and manage shared spaces, add or remove members, and organize channels within those spaces.

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

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

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

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step10 STEPS
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 Team Chat account and project
  • Basic familiarity with async Python/Typescript
2

Getting API Keys for OpenAI, Composio, and Zoom Team Chat

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
3

Installing dependencies

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

Create a new Typescript project and install the necessary dependencies:

  • @composio/llamaindex: Composio's LlamaIndex integration
  • @llamaindex/openai: OpenAI LLM integration
  • @llamaindex/tools: MCP client for LlamaIndex
  • @llamaindex/workflow: Workflow framework for LlamaIndex
  • dotenv: Environment variable management
4

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 Zoom Team Chat access
5

Import modules

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();

Create a new file called zoom team chat_llamaindex_agent.ts and import the required modules:

Key imports:

  • dotenv.config loads .env at runtime
  • readline gives us a simple CLI chat loop
  • Composio is the main Composio SDK client
  • mcp connects to an MCP endpoint
  • createAgent builds a LlamaIndex agent
  • openai configures the LLM backend
6

Load environment variables and initialize Composio

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");

What's happening:

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

7

Create a Tool Router session and build the agent function

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_chat"],
    },
  );

  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 Team Chat actions." ,
    llm,
    tools,
  });

  return agent;
}

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 team chat)
  • 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 Team Chat tools.
  • The MCP tools are mapped to LlamaIndex-compatible tools and plug them into the Agent.
8

Create an interactive chat loop

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();
}

What's happening:

  • We're creating a direct terminal interface to chat with Zoom Team Chat
  • The LLM's responses are streamed to the CLI for faster interaction.
  • The agent uses context to maintain conversation history
  • The agent processes the request, selects appropriate Zoom Team Chat tools, and returns a result
  • We extract the answer from the result data structure and display it to the user
  • You can type 'quit' or 'exit' to stop the chat loop gracefully
  • Agent responses and any errors are streamed in a clear, readable format
9

Define the main entry point

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

main();

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 Team Chat
10

Run the agent

npx ts-node llamaindex-agent.ts

When prompted, authenticate and authorise your agent with Zoom Team Chat, then start asking questions.

Complete Code

Here's the complete code to get you started with Zoom Team Chat and LlamaIndex:

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_chat"],
    },
  );

  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 Team Chat 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 Zoom Team Chat to LlamaIndex through Composio's Tool Router MCP layer. Key takeaways:
  • Tool Router dynamically exposes Zoom Team Chat 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.
TOOLS

Supported Tools

Every Zoom Team Chat action and event your agent gets out of the box.

Add Shared Space Members

Add members to a Zoom Team Chat shared space by email address or Zoom user ID.

Archive or Unarchive Channels

Archive or unarchive up to 10 Zoom Team Chat channels in one call.

Bookmark or Unbookmark Message

Add or remove a bookmark on a Zoom Team Chat message.

Create Channel

Create a new Zoom Team Chat channel for the authenticated user, optionally inviting initial members by email.

Create Message Reminder

Set a reminder on a Zoom Team Chat message, either after a delay (delay_seconds) or at an absolute time (remind_time).

Create Shared Space

Create a Zoom Team Chat shared space (a container that groups related channels).

Delete Channel

Delete a Zoom Team Chat channel the user owns or is a member of.

Delete Message

Delete a Zoom Team Chat message the connected user sent, identified by message_id plus the conversation it lives in.

Delete Message Reminder

Delete the reminder set on a Zoom Team Chat message.

Delete Scheduled Message

Delete a scheduled (draft) Zoom Team Chat message before it is sent, identified by draft_id plus the conversation it is addressed to.

Delete Shared Space

Delete a Zoom Team Chat shared space.

Get Channel

Get full information about a Zoom Team Chat channel, including its settings.

Get Chat Contact

Get a single Zoom Team Chat contact by email or user ID, optionally with live presence status.

Get Message

Get a single Zoom Team Chat message by ID, including its deep-link URL.

Get Message Thread

Retrieve a Zoom Team Chat message's thread: the parent message plus its replies since a given time.

Get Shared Space

Get details of a Zoom Team Chat shared space, including its owner and settings.

Invite Channel Members

Invite members to a Zoom Team Chat channel by email address.

Join Channel

Join a public Zoom Team Chat channel as the authenticated user.

Leave Channel

Leave a Zoom Team Chat channel.

List Bookmarks

List the authenticated user's bookmarked Zoom Team Chat messages, optionally filtered to one channel (to_channel) or one 1:1 contact (to_contact).

List Channel Members

List the members of a Zoom Team Chat channel.

List Channels

List the Zoom Team Chat channels the authenticated user is a member of.

List Chat Contacts

List the authenticated user's Zoom Team Chat contacts.

List Messages

List Zoom Team Chat messages exchanged in a channel or a 1:1 conversation, newest first (defaults to today).

List Pinned Messages

List the pinned messages of a Zoom Team Chat channel.

List Reminders

List the authenticated user's Zoom Team Chat message reminders.

List Scheduled Messages

List the user's scheduled (draft) Zoom Team Chat messages queued to send to a channel or a 1:1 contact.

List Chat Sessions

List the user's recent Zoom Team Chat sessions (channels and 1:1 conversations) within a time window.

List Shared Space Channels

List the channels grouped inside a Zoom Team Chat shared space.

List Shared Space Members

List the members and administrators of a Zoom Team Chat shared space.

List Shared Spaces

List the Zoom Team Chat shared spaces the authenticated user belongs to.

Mark Message Read or Unread

Mark a Zoom Team Chat message as read or unread.

Move Channels Into/Out of Shared Space

Move existing Zoom Team Chat channels into or out of a shared space.

Pin or Unpin Message

Pin or unpin a message in a Zoom Team Chat channel.

React to Message

Add or remove an emoji reaction on a Zoom Team Chat message.

Remove Channel Member

Remove a single member from a Zoom Team Chat channel.

Remove Shared Space Members

Remove members or administrators from a Zoom Team Chat shared space by user ID or member ID (the shared space owner cannot be removed).

Search Channels

Search Zoom Team Chat channels by name — fuzzy keywords or an exact channel name — across the channels the user has joined or the org's public channels.

Search Company Contacts

Search the connected user's organization directory for contacts by keyword (first name, last name, or email address).

Send Message

Send a Zoom Team Chat message to a channel or a 1:1 contact, optionally as a thread reply (reply_main_message_id) or scheduled for later (scheduled_time).

Star or Unstar Conversation

Star or unstar a Zoom Team Chat channel or contact for the authenticated user.

Update Channel

Rename a Zoom Team Chat channel or update its type/settings.

Update Message

Edit the text of an existing Zoom Team Chat message.

Update Shared Space

Update a Zoom Team Chat shared space's name, description, or settings.

FAQ

Frequently asked questions

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

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 Team Chat tools.

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

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

Start with Zoom Team Chat.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Zoom Team Chat tool your agent needs.Free to start.

Start building